Sandbox compatibility
Which Kubernetes versions and which upstream agent-sandbox version each DevZero sandbox release supports, and what the installer refuses.
Sandbox compatibility
The sandbox charts check these before they install anything. A refused install ends with a link to this page.
Matrix
Sandbox release (dz-sandbox, dz-sandbox-upstream) | agent-sandbox | Kubernetes |
|---|---|---|
| 0.1.2 | v1.0.11 | 1.30 or later |
| 0.1.1 | v1.0.11 | 1.30 or later |
Install both charts at the same release version. There is no upper Kubernetes bound: newer versions are accepted, and a provider suffix such as -eks-… counts as the version it carries.
Kubernetes 1.30 is the floor because the sandbox admission rules use ValidatingAdmissionPolicy, which is generally available from 1.30.
What the installer refuses
| Check | Chart | Refused when |
|---|---|---|
| Kubernetes version | both | the cluster is older than 1.30 |
| Upstream controller version | dz-sandbox | agent-sandbox-system/agent-sandbox-controller is missing, or runs a version other than the one this release was built and tested against (also a newer patch release) |
| Foreign controller | dz-sandbox-upstream | agent-sandbox-system already runs an agent-sandbox controller at another version that this release did not install |
Each release supports exactly one agent-sandbox version. To move to a newer agent-sandbox, upgrade both charts to the release that pins it, dz-sandbox-upstream first.
See Install self-hosted sandboxes for the full prerequisites.
Quickstart
Create a sandbox policy, then create a sandbox with the Python SDK, run a command, write and read a file, and delete it. Also connects an MCP client.
Policies and guardrails
How a SandboxPolicy governs a class of sandboxes, how cluster guardrails cap every policy, and why the sandbox namespace is the security boundary.