opentelemetry-python-instrumentation-fips

packaged by Chainguard

Chainguard Container for opentelemetry-python-instrumentation-fips

FIPS image with OpenTelemetry auto-instrumentation and instrumentation libraries for Python

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/opentelemetry-python-instrumentation-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 Chainguard opentelemetry-python-instrumentation-fips image is comparable to the upstream otel/autoinstrumentation-python image. The Chainguard image contains only the minimum set of tools and dependencies needed to function. This means it doesn't include things like a package manager.

Unlike upstream, this image ships only the glibc tree at /autoinstrumentation. The operator's instrumentation.opentelemetry.io/otel-python-platform: musl annotation copies /autoinstrumentation-musl, which this image does not carry, so that platform is unsupported.

FIPS Support

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

This image carries no interpreter of its own. The operator copies the instrumentation tree into your application pod, so crypto comes from the interpreter and the OpenSSL provider in that pod. Run the instrumented application on a FIPS-enabled base image, such as cgr.dev/ORGANIZATION/python-fips, for an end-to-end FIPS posture.

The instrumentation tree itself bundles no crypto library, so it adds no cryptography that Chainguard updates cannot reach. Python is an interpreted language, so review any additional dependency your application installs before you run it in a FIPS environment.

Prerequisites

This image does nothing on its own. It is a file donor: the OpenTelemetry Operator copies its instrumentation tree into your application pod.

• A Kubernetes cluster with the OpenTelemetry Operator installed. See the operator installation guide.
• A certificate source for the operator's admission webhooks: either cert-manager, or the operator chart's admissionWebhooks.autoGenerateCert.enabled value.
• A collector endpoint that accepts OTLP over HTTP. The bundle ships only the HTTP exporter.

Getting Started

This image is designed to work with the OpenTelemetry Operator for automatic Python application instrumentation in Kubernetes. The operator injects the instrumentation as an init container into your application pods.

To use this image, create an Instrumentation custom resource:

apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: python-instrumentation
  namespace: my-app-namespace
spec:
  exporter:
    endpoint: http://otel-collector:4318
  propagators:
    - tracecontext
    - baggage
  python:
    image: cgr.dev/ORGANIZATION/opentelemetry-python-instrumentation-fips:latest

Then annotate your Python application pods to enable auto-instrumentation:

apiVersion: v1
kind: Pod
metadata:
  name: my-python-app
  namespace: my-app-namespace
  annotations:
    instrumentation.opentelemetry.io/inject-python: "true"
spec:
  containers:
  - name: app
    image: cgr.dev/ORGANIZATION/python-fips:3.14
    command: ["python3", "-c", "import time; time.sleep(3600)"]

The operator will automatically inject an init container that copies the OpenTelemetry instrumentation packages into your application pod and configures the necessary environment variables (PYTHONPATH, OTEL_* variables) to enable automatic tracing.

The instrumentation tree carries wheels compiled for CPython 3.14. Run your instrumented application on a CPython 3.14 image, or the compiled modules will not load.

Documentation and Resources

• GitHub for upstream code
• Official Docs
• OpenTelemetry Operator 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.