Chainguard Container for jmx-exporter-bitnami-fips

The jmx-exporter-bitnami-fips Chainguard Image is used to expose JVM metrics for Prometheus to consume, as a helper container in any Bitnami Helm chart that supports jmx metrics.

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/jmx-exporter-bitnami-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

This image is a FIPS version of the JMX Exporter image and requires specific keystore settings to ensure it functions in a FIPS compliant manner. Like the non-FIPS JMX exporter image, it is comparable to the Bitnami jmx-exporter iamge.

Getting Started

You can deploy this image using the Bitnami Kafka Helm chart by some overridden settings, as follows:

cat <<EOF > values.yaml
global:
  security:
    allowInsecureImages: true
image:
  registry: "cgr.dev/ORGANIZATION"
  repository: "kafka"
  tag: "latest"
externalAccess:
  image:
    registry: "cgr.dev/ORGANIZATION"
    repository: "kubectl-bitnami"
    tag: "latest"
metrics:
      jmx:
        enabled: "true"
        image:
          registry: "cgr.dev/ORGANIZATION"
          repository: "jmx-exporter-bitnami-fips"
          tag: "latest"
EOF
helm install kafka-jmx oci://registry-1.docker.io/bitnamicharts/kafka --values values.yaml

Enabling FIPS‑Compliant TLS for JMX Exporter Using BCFKS

This image can be configured to use a FIPS‑enabled keystore (BCFKS) for TLS on the JMX metrics endpoint.

Configuring JMX Exporter for TLS

In your Helm values (or custom ConfigMap), configure the JMX exporter to use TLS by referencing the keystore:

metrics:
  jmx:
    enabled: "true"
    image:
      registry: "cgr.dev"
      repository: "jmx-exporter-bitnami-fips"
      tag: "latest"
      pullPolicy: Always
    config: |
      sslKeyStore: "/tmp/jmx_exporter.bcfks"
      sslKeyStorePassword: "changeit"
      sslTrustStore: "/tmp/jmx_exporter.bcfks"
      sslTrustStorePassword: "changeit"
      lowercaseOutputName: true
      hostPort: "0.0.0.0:5556"
      rules:
        - pattern: ".*"
      httpServer:
        ssl:
          keyStore:
            filename: /tmp/jmx_exporter.bcfks
          certificate:
            alias: jmx-exporter

Patching the JMX Exporter Container

You need to ensure that the keystore is generated at container startup. To do this, you can patch the StatefulSet for the JMX exporter container so that it first runs the keytool command and then starts the exporter with the proper TLS flags. An example patch file (patch.yaml) might look like this:

spec:
  template:
    spec:
      containers:
      - name: jmx-exporter
        command: ["/bin/sh", "-c"]
        args:
          - |
            keytool -genkeypair -alias jmx-exporter \
              -keyalg RSA -keysize 2048 -storetype BCFKS \
              -keystore /tmp/jmx_exporter.bcfks -storepass changeit \
              -keypass changeit -dname "CN=localhost" -validity 365 && \
            java -cp "/usr/share/java/bouncycastle-fips/*" \
              -Djavax.net.ssl.trustStoreType=BCFKS \
              -Djavax.net.ssl.keyStoreType=BCFKS \
              -Djavax.net.ssl.trustStore=/tmp/jmx_exporter.bcfks \
              -Djavax.net.ssl.trustStorePassword=changeit \
              -Djavax.net.ssl.keyStore=/tmp/jmx_exporter.bcfks \
              -Djavax.net.ssl.keyStorePassword=changeit \
              -jar jmx_prometheus_standalone.jar 5556 /etc/jmx-kafka/jmx-kafka-prometheus.yml
        readinessProbe:
            httpGet:
              scheme: HTTPS

After installing the Helm chart, you can apply this patch to your broker and controller StatefulSets:

kubectl patch sts/kafka-broker --patch-file patch.yaml
kubectl patch sts/kafka-controller --patch-file patch.yaml

Connecting to the TLS‑Enabled JMX Metrics Endpoint

Once deployed, verify that the JMX exporter is serving metrics over TLS on port 5556 by using a TLS client:

openssl s_client -connect 127.0.0.1:5556 -tls1_2

Or test with curl (ignoring certificate validation):

curl -sik https://<your-service>:5556/metrics

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.