Chainguard Container for istio-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/istio-fips:latest

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

Istio Images

• cgr.dev/ORGANIZATION/istio-install-cni-fips: Installs the CNI plugin with OpenSSL FIPS provider for sidecar injection without NET_ADMIN.
• cgr.dev/ORGANIZATION/istio-pilot-fips: Istio Pilot for service discovery and config distribution comes with FIPS compliance
• cgr.dev/ORGANIZATION/istio-proxy-fips: Hardened Envoy proxy with FIPS support
• cgr.dev/ORGANIZATION/istio-operator-fips: Operator to manage Istio via CRDs that supports FIPS.

FIPS Support

The Istio Chainguard Images ships with a validated redistribution of the OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

Installation with Helm

These images can be used by overriding the default image values in the official Istio Helm charts.

First, add the Istio Helm repository:

helm repo add istio https://istio-release.storage.googleapis.com/charts
helm repo update

Then install Istio using a single helm install command. Below is a basic example installing the Istio base, control plane, and CNI plugin.

helm install istio-base istio/base -n istio-system --create-namespace

helm install istiod istio/istiod -n istio-system \
  --set global.proxy.image=cgr.dev/ORGANIZATION/istio-proxy-fips \
  --set pilot.image=cgr.dev/ORGANIZATION/istio-pilot-fips

helm install istio-cni istio/cni -n istio-system \
  --set cni.enabled=true \
  --set cni.image=cgr.dev/ORGANIZATION/istio-install-cni-fips \
  --set cni.cniConfDir="/var/lib/rancher/k3s/agent/etc/cni/net.d" \
  --set cni.cniBinDir="/opt/cni/bin"

To use the Istio Operator:

helm install istio-operator istio/operator -n istio-operator-system --create-namespace \
  --set operator.image=cgr.dev/chainguard-private/istio-operator-fips

Installation with Helm Using values.yaml

If you prefer to keep your customisations in a file instead of long --set strings, create a small values.yaml for each chart you install.

Why one file per chart?
The Istio Helm repository publishes separate charts (base, istiod, cni, operator).
Each chart has its own values schema, so you pass the file that matches the chart you’re installing.

istiod-values.yaml

# istiod-values.yaml
global:
  proxy:
    image: cgr.dev/ORGANIZATION/istio-proxy-fips     # Envoy + iptables
pilot:
  image: cgr.dev/ORGANIZATION/istio-pilot-fips       # Control-plane

Install:

helm install istiod istio/istiod \
  -n istio-system -f istiod-values.yaml

istio-cni-values.yaml

# istio-cni-values.yaml
cni:
  enabled: true
  image: cgr.dev/ORGANIZATION/istio-install-cni-fips
  cniConfDir: /var/lib/rancher/k3s/agent/etc/cni/net.d
  cniBinDir: /opt/cni/bin

Install:

helm install istio-cni istio/cni \
  -n istio-system -f istio-cni-values.yaml

istio-operator-values.yaml

# istio-operator-values.yaml
operator:
  image: cgr.dev/ORGANIZATION/istio-operator-fips

Install:

helm install istio-operator istio/operator \
  -n istio-operator-system --create-namespace \
  -f istio-operator-values.yaml

Documentation and Resources

You can learn more about Istio by following the official documentation.
If you’re working with the operator, the IstioOperator API reference is useful.
For advanced Helm tuning, consult the installation‑options reference.

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.