zalando-pgbouncer-fips

packaged by Chainguard

Chainguard Container for zalando-pgbouncer-fips

FIPS-validated postgres-operator, logical-backup and zalando-pgbouncer connection-pooler images that create and manage PostgreSQL clusters in Kubernetes, with scheduled pg_dumpall backups to object storage.

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/zalando-pgbouncer-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

Comparable to the upstream postgres-operator image and its logical-backup sidecar, built with FIPS-validated cryptography. Both run as Chainguard's non-root user 65532 a deliberate hardening difference from upstream with no functional impact:

• postgres-operator-fips runs 65532; upstream runs 1000:1000.
• postgres-operator-fips-logical-backup runs 65532; upstream runs as root.
• zalando-pgbouncer-fips (the connection pooler the operator deploys when a cluster sets enableConnectionPooler) runs as uid 100 / gid 101, matching the securityContext the operator enforces on pooler pods. It implements the operator 2.x pooler contract: the pgbouncer configuration is rendered from operator-injected environment variables and the pooler credentials are consumed from the userlist the operator mounts at /etc/pgbouncer/userlist.txt. Operators older than 2.0 pass credentials via a PGPASSWORD environment variable instead and are not compatible with this pooler image.

FIPS Support

The postgres-operator-fips Chainguard Image ships 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.

Because FIPS-hardened OpenSSL disables MD5, the logical-backup client cannot use md5 password authentication — configure clusters this operator backs up to use scram-sha-256 (spec.postgresql.parameters.password_encryption).

The same applies to the zalando-pgbouncer-fips pooler: its only cryptography is the system OpenSSL, constrained to the FIPS-validated provider for both the TLS it serves and client authentication. With scram-sha-256 clusters, the pooler's auth_query hands SCRAM secrets to pgbouncer, keeping MD5 off the wire. If the FIPS configuration is removed or corrupted, the pooler entrypoint's certificate generation fails rather than falling back to non-approved algorithms.

Getting Started

Deploy the operator with the upstream postgres-operator Helm chart, pointed at the Chainguard FIPS operator and logical-backup images:

# values.yaml
image:
  registry: cgr.dev
  repository: ORGANIZATION/postgres-operator-fips
  tag: latest
configLogicalBackup:
  logical_backup_docker_image: cgr.dev/ORGANIZATION/postgres-operator-fips-logical-backup:latest
configConnectionPooler:
  connection_pooler_image: cgr.dev/ORGANIZATION/zalando-pgbouncer-fips:latest

helm repo add postgres-operator-charts https://opensource.zalando.com/postgres-operator/charts/postgres-operator
helm install postgres-operator postgres-operator-charts/postgres-operator \
  --namespace postgres-operator --create-namespace \
  --values values.yaml

Documentation and Resources

• postgres-operator documentation
• FIPS-enabled Chainguard Containers

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.