ingress-nginx-opentelemetry

packaged by Chainguard

Chainguard Image for ingress-nginx-opentelemetry

This image only contains the necessary files to be copied to Ingress Controller deployment when OpenTelemetry is enabled

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/ingress-nginx-opentelemetry:latest

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

This image is a replacement for registry.k8s.io/ingress-nginx/opentelemetry and is intended to be used in conjunction with ingress-nginx.

Helm

helm upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx --create-namespace \
  --set "opentelemetry.image.registry=cgr.dev" \
  --set "opentelemetry.image.image=chainguard-private/ingress-nginx-opentelemetry" \
  --set "opentelemetry.image.digest=$(crane digest cgr.dev/chainguard-private/ingress-nginx-opentelemetry:latest)"

yaml

If deploying using yaml manifests, this image is intended to be used as the opentelemetry initContainer in the ingress-nginx-controller deployment.

initContainers:
  - command:
      - /init_module
    image: cgr.dev/chainguard-private/ingress-nginx-opentelemetry@sha256:8b09c413660c6bfd47048697c055bada4ab28396151459893a517e30907b5dfe
    imagePullPolicy: IfNotPresent
    name: opentelemetry
    resources: {}
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
          - ALL
      readOnlyRootFilesystem: true
      runAsNonRoot: true
      runAsUser: 65532
      seccompProfile:
        type: RuntimeDefault
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
      - mountPath: /modules_mount
        name: modules

FIPS

This image does not have or need a FIPS variant.

This image is used to copy dynamically linked libraries to the ingress-nginx-controller container at runtime, so it does not need FIPS-enabled cryptography included. Instead, this image should be paired with ingress-nginx-controller-fips for a FIPS-enabled deployment.

e.g.

helm upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx --create-namespace \
  --set "opentelemetry.image.registry=cgr.dev" \
  --set "opentelemetry.image.image=chainguard-private/ingress-nginx-opentelemetry" \
  --set "opentelemetry.image.digest=$(crane digest cgr.dev/chainguard-private/ingress-nginx-opentelemetry:latest)"
  --set image.repository=cgr.dev/chainguard/ingress-nginx-controller-fips

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

• Minimal design, with no unnecessary software bloat
• Automated nightly builds to ensure Images are completely up-to-date and contain all available security patches
• High quality build-time SBOMs (software bills of materials) attesting the provenance of all artifacts within the Image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.