NewCompare CPU & GPU pricing across AWS, Azure & GCP
Self-hosted sandboxes

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-sandboxKubernetes
0.1.2v1.0.111.30 or later
0.1.1v1.0.111.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

CheckChartRefused when
Kubernetes versionboththe cluster is older than 1.30
Upstream controller versiondz-sandboxagent-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 controllerdz-sandbox-upstreamagent-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.

On this page