Agent Substrate Moves ActorTemplate From Kubernetes CRD to Native ateapi Resource

As of September 2, 2026, the ActorTemplate object is no longer a Kubernetes custom resource definition (CRD) and has been migrated to the ateapi layer within Agent Substrate. The change was made because hosting ActorTemplate as a Kubernetes object caused it to inherit incorrect identity, naming, lifecycle, and auth conventions, preventing CLI, SaaS, and gRPC clients from sharing a unified API surface. Templates are now defined as YAML configurations and managed directly through the ate-api-server via dedicated ateapi controls such as CreateActorTemplate and ListActorTemplates. Developers can create templates using the kubectl ate create actor-template command and then provision Actors referencing those templates within a specified atespace. The migration allows the template schema to evolve independently of Kubernetes while keeping Actors and their templates under a consistent ateapi ownership model.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in