Dynamic containers
Running deployments can now host dynamic containers: containers your backend creates through the API, separate from releases. Use them for per-tenant workers, jobs, or anything you start on demand.
The stack decides what's allowed. It approves the image repositories and picks the compute pool, so a caller can't run an arbitrary image or choose where it lands.
The API puts, gets, lists, and deletes containers, and reads their logs. The typed methods are in the Platform API SDK. Dynamic containers have their own lifecycle, separate from the resources a release manages.
- Restricted by default: on Kubernetes, they run with restricted security settings and namespace-scoped permissions