Deploying an Agent Substrate Actor After ActorTemplate Left Kubernetes

Agent Substrate has announced a significant architectural shift regarding how Actors are deployed. As of September 2, 2026, the ActorTemplate object has been removed from Kubernetes, transitioning from a Kubernetes Custom Resource Definition (CRD) to an internal ateapi resource. This change aims to decouple the template schema from Kubernetes-specific conventions, allowing for better evolution of the API across CLI, SaaS, and gRPC clients. Developers can now manage templates directly through the ate-api-server using commands like 'kubectl ate create actor-template'. The update requires users to define templates via YAML configurations that specify worker selectors, container settings, and resource limits. By moving these templates into the ateapi, the project aims to improve the separation of concerns, ensuring that the infrastructure layer remains distinct from the application-specific logic required for managing Agent Substrate Actors.