Chainguard Container for prometheus-blackbox-exporter-iamguarded-fips

Prometheus blackbox exporter allows blackbox probing of endpoints over HTTP, HTTPS, DNS, TCP, ICMP and gRPC.

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/prometheus-blackbox-exporter-iamguarded-fips:latest

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

FIPS support

The prometheus-blackbox-exporter-iamguarded-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.

Overview

Prometheus Blackbox Exporter IAMGuarded is a security-enhanced variant of the Blackbox Exporter designed to be deployed using the Kube-Prometheus IAMGuarded Helm chart. This image provides additional security benefits over standard Blackbox Exporter deployments and allows blackbox probing of endpoints over HTTP, HTTPS, DNS, TCP, and ICMP.

Kube-Prometheus Helm Chart Usage

This image is primarily used with the Kube-Prometheus IAMGuarded Helm chart, which provides a complete Prometheus monitoring stack including Prometheus server, Alertmanager, Prometheus Operator, Node Exporter, Kube State Metrics, and Blackbox Exporter.

Installation

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

Important: Replace $ORGANIZATION with your Chainguard organization name.

Blackbox Exporter Configuration

When using the Kube-Prometheus chart, you can override the Blackbox Exporter image under the blackboxExporter section in your values.yaml:

blackboxExporter:
  image:
    registry: cgr.dev
    repository: $ORGANIZATION/prometheus-blackbox-exporter-iamguarded-fips
    digest: sha256:... # Use specific digest for production

Image Override in Complete Kube-Prometheus Configuration

global:
  org: $ORGANIZATION

prometheus:
  image:
    registry: cgr.dev
    repository: $ORGANIZATION/prometheus-iamguarded-fips
    digest: sha256:...

alertmanager:
  image:
    registry: cgr.dev
    repository: $ORGANIZATION/prometheus-alertmanager-iamguarded-fips
    digest: sha256:...

operator:
  image:
    registry: cgr.dev
    repository: $ORGANIZATION/prometheus-operator-iamguarded-fips
    digest: sha256:...

"node-exporter":
  image:
    registry: cgr.dev
    repository: $ORGANIZATION/prometheus-node-exporter-iamguarded-fips
    digest: sha256:...

"kube-state-metrics":
  image:
    registry: cgr.dev
    repository: $ORGANIZATION/kube-state-metrics-iamguarded-fips
    digest: sha256:...

blackboxExporter:
  image:
    registry: cgr.dev
    repository: $ORGANIZATION/prometheus-blackbox-exporter-iamguarded-fips
    digest: sha256:...

Authentication

Ensure proper pull credentials are configured through one of the following methods:

Option 1: Using Helm values with global.imagePullSecrets

# values.yaml
global:
  imagePullSecrets:
    - name: chainguard-pull-secret

Option 2: Create a Kubernetes pull secret

# Step 1: Authenticate with chainctl and generate a pull token
chainctl auth login
chainctl auth configure-docker --pull-token --save --ttl=24h

# Step 2: Create the Kubernetes secret
kubectl create secret docker-registry chainguard-pull-secret \
  --docker-server=cgr.dev \
  --docker-username=$(echo cgr.dev | docker-credential-cgr get | jq -r '.Username') \
  --docker-password=$(echo cgr.dev | docker-credential-cgr get | jq -r '.Secret') \
  -n <your-namespace>

For more details on the complete monitoring stack configuration, refer to the Kube-Prometheus chart's values.yaml file.

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.