Chainguard Container for prometheus-pgbouncer-exporter-fips

A FIPS-compliant image for PgBouncer Exporter. A Prometheus exporter that collects and exposes metrics from PgBouncer, a lightweight connection pooler for PostgreSQL

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-pgbouncer-exporter-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 compatible with the upstream quay.io/prometheuscommunity/pgbouncer-exporter Image. However, the Chainguard image contains only the minimum set of tools and dependencies needed to function. This means it doesn't include things like a package manager. Switching to Chainguard's prometheus-pgbouncer-exporter-fips image should not require any changes to your existing setup.

FIPS Support

The PgBouncer Exporter FIPS Chainguard Image 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

Usage Instructions

To use the PgBouncer Exporter, you'll need a working PgBouncer setup in your Environment.

PGBouncer configuration

The PgBouncer-Exporter requires a configuration change to pgbouncer to ignore a PostgreSQL driver connection parameter. In the pgbouncer.ini please include this option:

   ignore_startup_parameters = extra_float_digits

Run with docker

docker run ORGANIZATION/prometheus-pgbouncer-exporter-fips:latest <flags>

Helm

To deploy prometheus-pgbouncer-exporter on your Kubernetes cluster using Chainguard's prometheus-pgbouncer-exporter-fips image, you can use the the upstream Helm chart from the Prometheus Community repository.

To use the Chainguard image, override the image repository and tag in your own values.yaml file:

image:
    repository: ORGANIZATION/prometheus-pgbouncer-exporter-fips
    tag: latest

Deploy PgBouncer-Exporter with Helm:

helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update
helm install pgbouncer-exporter prometheus-community/prometheus-pgbouncer-exporter -f values.yaml
kubectl rollout status deployment/prometheus-pgbouncer-exporter

Once PgBouncer-Exporter is up and running, you can validate metrics from Host:

kubectl port-forward -n pgbouncer-demo svc/prometheus-pgbouncer-exporter 8080:9127 &
curl http://localhost:8080/metrics

Documentation and Resources

• Official documentation for pgbouncer-exporter project
• Metrics Documentation
• GoDoc / API docs
• GitLab Docs (usage in Gitlab)

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.