ingress-nginx-controller-fips

Chainguard Container for ingress-nginx-controller-fips

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/ingress-nginx-controller-fips:latest

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

Getting Started

The ingress-nginx-controller-fips Chainguard image is a FIPS compliant variant of the ingress-nginx image from the kubernetes.github.io/ingress-nginx repository.

This image benefits from inclusion in Chainguard's EmeritOSS Program. When the upstream Ingress-NGINX project is archived in March of 2026, Chainguard will continue to maintain a fork of ingress-nginx at https://github.com/chainguard-forks/ingress-nginx. At that point, Chainguard's Ingress-NGINX Controller FIPS image and the underlying package will be based on Chainguard's fork of ingress-nginx, extending the useful life of this image.

To install with the upstream Helm chart you could run the following commands:

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
cat <<EOF > values.yaml
controller:
  image:
    registry: cgr.dev
    image: ORGANIZATION/ingress-nginx-controller-fips
    tag: latest
    digest: null
EOF
helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx -f values.yaml

Rather than using latest we recommend using a named version and setting the digest value as appropriate. To keep the version and digest updated automatically you can use Renovate or Digestabot.

Chainguard also offers a -debug variant of this image with debug symbols for nginx, required by observability tools like Dynatrace for runtime instrumentation.

ingress-nginx-custom-error-pages-fips

The ingress-nginx-custom-error-pages-fips Chainguard image is a FIPS compliant variant of the upstream registry.k8s.io/ingress-nginx/custom-error-pages image.

To install with the upstream helm chart you could use the following values.yaml:

cat <<EOF > values.yaml
defaultBackend:
  enabled: true
  image:
    registry: cgr.dev
    image: ORGANIZATION/ingress-nginx-custom-error-pages-fips
    tag: latest
EOF

For more information about the Custom Errors image, please refer to the official 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.