cloudzero-agent-fips

packaged by Chainguard

Chainguard Container for cloudzero-agent-fips

Minimal FIPS-enabled CloudZero Agent image — a Kubernetes cost-monitoring and telemetry collector for the CloudZero platform.

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/cloudzero-agent-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

Chainguard's cloudzero-agent-fips is the FIPS-enabled variant of the cloudzero-agent image — a minimal, mono-image build of the CloudZero Agent components for the CloudZero platform. It runs as the non-root user nobody from the working directory /app and is shell-less with few-to-zero CVEs.

The CloudZero component binaries are built with a FIPS-validated Go toolchain and installed at /usr/bin/<name>-fips, but their /app/<name> compat symlinks match the upstream (and standard image) paths — for example /app/cloudzero-collector resolves to the FIPS cloudzero-collector binary. The image is therefore a drop-in replacement for the standard cloudzero-agent image: the default command is /app/cloudzero-agent-validator, and the cloudzero-agent Helm chart's workload commands run unchanged, with no per-workload overrides required. The bundled Grafana Alloy (/app/cloudzero-alloy) and prometheus-operator config-reloader (/app/prometheus-config-reloader) also keep the upstream /app names.

Like the standard image, it differs from the upstream image in a few ways worth noting:

• It ships one additional binary, cloudzero-regurgitator (an upstream CloudZero tool the upstream image does not include), so it carries 12 /app binaries versus upstream's 11.
• The bundled companions are slightly ahead of upstream's pins: Grafana Alloy 1.19.2 (upstream builds v1.18.1) and the prometheus-operator config-reloader 0.94.0 (upstream builds v0.91.0).
• Bundling Grafana Alloy pulls in its runtime dependencies, including the xz, zstd, and lz4 compression utilities, so the image is larger than the upstream agent image.

The bundled Alloy is Chainguard's grafana-alloy-fips, which does not carry CloudZero's custom discovery.kubestate Alloy component, so the chart's optional clustered kubeState mode is not supported by this image.

FIPS Support

This Chainguard Container is built with a FIPS-validated Go toolchain and links the system OpenSSL FIPS provider, so its cryptographic operations are performed by FIPS 140-3 validated modules. For more on FIPS support in Chainguard Containers, refer to the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

The CloudZero Agent collects Kubernetes cost and telemetry data and ships it to the CloudZero platform, deployed with the cloudzero-agent Helm chart.

Add the chart repository:

helm repo add cloudzero https://cloudzero.github.io/cloudzero-charts
helm repo update

Create a values file that points every component the chart deploys at its FIPS Chainguard image, then supply your CloudZero credentials. Overriding only components.agent would leave the Prometheus and kube-state-metrics workloads non-FIPS, so set those to their -fips images too:

cat > values.yaml <<EOF
components:
  agent:
    image:
      repository: cgr.dev/ORGANIZATION/cloudzero-agent-fips
  prometheus:
    image:
      repository: cgr.dev/ORGANIZATION/prometheus-fips
      tag: latest
kubeStateMetrics:
  image:
    registry: cgr.dev
    repository: ORGANIZATION/kube-state-metrics-fips
    tag: latest
apiKey: <CLOUDZERO_API_KEY>
clusterName: <CLUSTER_NAME>
cloudAccountId: "<CLOUD_ACCOUNT_ID>"
region: <REGION>
EOF

Then install the chart:

helm install cloudzero-agent cloudzero/cloudzero-agent \
  --namespace cloudzero-agent --create-namespace \
  --values values.yaml

Deploying the agent requires:

• A CloudZero API key with the container-metrics_v1:abandon, container-metrics_v1:get-status, container-metrics_v1:legacy, container-metrics_v1:upload, and insights:read_insights scopes.
• The cluster name, cloud account id, and region.
• Egress on port 443 from the agent-server, aggregator, and confload pods to https://api.cloudzero.com and *.s3.amazonaws.com.

Documentation and Resources

• CloudZero Agent GitHub repository
• CloudZero Agent Helm chart
• CloudZero platform 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.