Chainguard Container for tetragon-fips

FIPS-Complaint Images for Tetragon. eBPF-based Security Observability and Runtime Enforcement

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/tetragon-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

Tetragon FIPS is comprised of 2 images:

• cgr.dev/ORGANIZATION/tetragon-fips
• cgr.dev/ORGANIZATION/tetragon-operator-fips

The Chainguard images usually do not run as the root user and contain only the minimum set of tools and dependencies needed to function. This means they do not include utilities such as a shell or a package manager.

The Chainguard's tetragon-fips image is still configured to run as root because it requires elevated kernel capabilities in order to:

• Load and attach eBPF programs.
• Access host namespaces.
• Perform other privileged operations. In practice, this functionality requires running as a privileged container on Kubernetes, which inherently implies root access inside the container.

The Chainguard's tetragon-operator-fips image, however, is configured to run as nonroot. Its functionality has been validated under these restrictions, ensuring that it maintains Chainguard’s security standards without requiring elevated privileges.

FIPS Support

The Tetragon FIPS Chainguard Images is shipped 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

Getting Started

There are multiple ways of deploying Tetragon but the recommended way is to use the official Helm Chart for Tetragon.

Deployment using Helm Chart

To deploy Tetragon, run the following instructions: Start by adding a values.yaml file to override with Chainguard's image:

# values.yaml
tetragon
  image:
    repository: cgr.dev/<ORGANIZATION>/tetragon-fips
    tag: latest
tetragonOperator:
  image:
    repository: cgr.dev/<ORGANIZATION>/tetragon-operator-fips
    tag: latest

Deploy Tetragon with Helm:

helm repo add cilium https://helm.cilium.io
helm repo update
helm install tetragon cilium/tetragon -n kube-system -f values.yaml
kubectl rollout status -n kube-system ds/tetragon -w

Once Tetragon and Tetragon-Operator have been deployed successfully, you can deploy a demo application to have sample workload:

kubectl create -f https://raw.githubusercontent.com/cilium/cilium/main/examples/minikube/http-sw-app.yaml

Once the demo application related pods are up, you can observe Tetragon execution events:

kubectl exec -it -n kube-system ds/tetragon -c tetragon -- tetra getevents -o compact --pods xwing

You are now up and running with Chainguard's Tetragon images!

Documentation and Resources

• Getting Started
• Tetragon Events
• Tracing Policy
• Tetragon Runtime Hooks
• Documentation for Tetragon enforcement system
• Policy Library
• Use Cases
• Low level reference documentation for Tetragon

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.