jaeger-iamguarded

Chainguard Container for jaeger-iamguarded

CNCF Jaeger Distributed Tracing Platform - IAMGuarded variant

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/jaeger-iamguarded:latest

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

Overview

Jaeger IAMGuarded is a security-enhanced variant of Jaeger designed to be deployed using its companion IAMGuarded Helm chart. This is a single container image that includes all core Jaeger component binaries, allowing flexible deployment configurations through the Helm chart.

The Helm chart can be configured to run the image with different entrypoints to deploy these components separately or together.

Helm Chart Installation

The Jaeger IAMGuarded Helm chart is delivered exclusively through the same OCI registry as your Chainguard images:

cgr.dev/$ORGANIZATION/iamguarded-charts/jaeger

Basic Installation

Once authenticated (see below) you can install the chart with standard Helm commands and your organization name:

helm install jaeger oci://cgr.dev/$ORGANIZATION/iamguarded-charts/jaeger \
  --set "global.org=$ORGANIZATION"

Important: Replace $ORGANIZATION with your Chainguard organization name. The default organization in the chart values is chainguard-private, which must be changed to match your organization.

Configuration Requirements

Organization Setting

The global.org value is required and can be set either:

• Via --set flag during installation
• In your existing values.yaml file

Registry Configuration

For users who mirror images to custom repositories:

• Use global.imageRegistry to override the default cgr.dev
• For complex mirroring strategies, consult the chart's values.yaml for image configuration options including registry, repository, tag, and digest

Example values.yaml for custom registry configuration:

# Single jaeger-iamguarded image used for all components
image:
  registry: myregistry.example.com
  repository: mirrored/jaeger-iamguarded
  digest: sha256:...

# Note: The same image is used for all deployment modes (collector, query, ingester, allInOne)
# The chart configures different entrypoints and commands for each component

Authentication

For detailed instructions on configuring authentication and pull credentials for iamguarded images, please refer to our comprehensive guide:

How to Use Chainguard Helm Charts

Best Practices

1. Pin to Digest: While charts follow the same tagging scheme as Chainguard images, always pin to a specific chart digest to prevent unexpected updates:

   helm install jaeger oci://cgr.dev/$ORGANIZATION/iamguarded-charts/jaeger@sha256:DIGEST \
     --set "global.org=$ORGANIZATION"

   The digest can be found in the output of helm pull e.g:

   helm pull oci://cgr.dev/$ORGANIZATION/iamguarded-charts/jaeger
   Pulled: cgr.dev/chainguard-private/iamguarded-charts/jaeger:1.65.0
   Digest: sha256:...

2. Review Default Values: The chart provides security-minded defaults that are sensible but may not be production-ready for all use cases. Review the chart's values.yaml (run helm show values) for the full range of configuration options.

Validation

After deployment, validate your Jaeger IAMGuarded installation:

# Check pod status
kubectl get pods -l app.kubernetes.io/name=jaeger

# Access the Jaeger UI (if using port-forward)
kubectl port-forward svc/jaeger-query 16686:16686

# Visit http://localhost:16686 to access the Jaeger UI

Security Considerations

The Jaeger IAMGuarded chart provides security-minded defaults while acknowledging the cluster-specific nature of both Jaeger and Kubernetes environments. Review and adjust settings based on your specific security requirements and cluster configuration.

For detailed configuration options and advanced usage, refer to the chart's values.yaml file.

Usage Examples

Production Deployment

For production, deploy collector and query components separately with a persistent storage backend:

helm install jaeger oci://cgr.dev/$ORGANIZATION/iamguarded-charts/jaeger \
  --set "global.org=$ORGANIZATION" \
  --set "collector.enabled=true" \
  --set "query.enabled=true" \
  --set "storage.type=elasticsearch" \
  --set "storage.elasticsearch.host=elasticsearch.default.svc.cluster.local"

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.