envoy-ai-gateway-extproc-fips

packaged by Chainguard

Chainguard Container for envoy-ai-gateway-extproc-fips

FIPS-enabled Envoy AI Gateway controller and external processor, built against the FIPS-validated openssl provider.

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/envoy-ai-gateway-extproc-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

These images expose the same CLI, configuration, and runtime behaviour as their non-FIPS counterparts; only the cryptographic provider differs. Charts and manifests written for the upstream envoyproxy/ai-gateway-controller and envoyproxy/ai-gateway-extproc images work without modification.

Getting Started

Envoy AI Gateway is composed of two container images:

cgr.dev/ORGANIZATION/envoy-ai-gateway-controller-fips:latest
cgr.dev/ORGANIZATION/envoy-ai-gateway-extproc-fips:latest

The controller is a Kubernetes controller that reconciles AIGatewayRoute and AIServiceBackend resources into Envoy Gateway primitives; the external processor (extproc) is the Envoy ext_proc filter that rewrites and routes LLM requests at the data plane.

Envoy AI Gateway depends on Envoy Gateway, which Chainguard also publishes as a FIPS variant:

cgr.dev/ORGANIZATION/envoy-gateway-fips:latest

Install the prerequisite Envoy Gateway chart, the Envoy AI Gateway CRDs, then Envoy AI Gateway with both Chainguard images:

helm install envoy-gateway oci://docker.io/envoyproxy/gateway-helm \
  --namespace envoy-gateway-system --create-namespace \
  --set deployment.envoyGateway.image.repository=cgr.dev/ORGANIZATION/envoy-gateway-fips \
  --set deployment.envoyGateway.image.tag=latest

helm install ai-gateway-crds oci://docker.io/envoyproxy/ai-gateway-crds-helm \
  --namespace envoy-ai-gateway-system --create-namespace

helm install ai-gateway oci://docker.io/envoyproxy/ai-gateway-helm \
  --namespace envoy-ai-gateway-system \
  --set controller.image.repository=cgr.dev/ORGANIZATION/envoy-ai-gateway-controller-fips \
  --set controller.image.tag=latest \
  --set extProc.image.repository=cgr.dev/ORGANIZATION/envoy-ai-gateway-extproc-fips \
  --set extProc.image.tag=latest

Documentation and Resources

Refer to the Envoy AI Gateway documentation for configuration, supported providers, and the full set of AIGatewayRoute and AIServiceBackend options. For FIPS background and Chainguard's approach, see the Chainguard FIPS documentation.

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.