agent-sandbox-fips

packaged by Chainguard

Chainguard Container for agent-sandbox-fips

FIPS-enabled Kubernetes controller for isolated, stateful, singleton workloads such as AI agent runtimes and reinforcement learning (RL) environments

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/agent-sandbox-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The agent-sandbox-fips image is comparable to registry.k8s.io/agent-sandbox/agent-sandbox-controller. It preserves the upstream /agent-sandbox-controller entrypoint, UID 65532, and /home/nonroot working directory. This image contains the controller, not the sandbox workloads or the separate sandbox-router component. Isolation runtimes such as gVisor or Kata must be configured in your cluster separately.

FIPS Support

The agent-sandbox-fips Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Prerequisites

You need a Kubernetes cluster, Helm 3, Git, kubectl, and permission to install CRDs and cluster-wide RBAC. Configure your cluster to pull cgr.dev/ORGANIZATION/agent-sandbox-fips using your organization's registry credentials. The upstream Helm chart is distributed in the source repository.

Getting Started

Replace ORGANIZATION with your registry organization and REPLACE_WITH_VERSION with a release available in the Chainguard catalog, without the leading v. Use the same release for the image and chart source:

VERSION="REPLACE_WITH_VERSION"
git clone --depth 1 --branch "v${VERSION}" \
  https://github.com/kubernetes-sigs/agent-sandbox.git

cat > agent-sandbox-values.yaml <<EOF
image:
  repository: cgr.dev/ORGANIZATION/agent-sandbox-fips
  tag: ${VERSION}
namespace:
  create: false
controller:
  extensions: true
EOF

helm install agent-sandbox ./agent-sandbox/helm \
  --namespace agent-sandbox-system --create-namespace \
  --values agent-sandbox-values.yaml --wait

kubectl rollout status deployment/agent-sandbox-controller \
  --namespace agent-sandbox-system --timeout=180s

Helm installs the CRDs and controller RBAC. The controller can now manage Sandboxes, SandboxTemplates, SandboxWarmPools, and SandboxClaims. Follow the upstream examples to create a workload. If your cluster uses a registry pull secret, set imagePullSecrets in the values file.

Configuration

The example enables extension controllers with controller.extensions; omit it for core Sandboxes only. namespace.create: false lets Helm's --create-namespace manage the release namespace. Metrics use port 8080, and health/readiness probes use port 8081. See the chart values and controller configuration for available options.

Documentation and Resources

• Agent Sandbox documentation
• Agent Sandbox on GitHub

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.