Chainguard Container for plugin-barman-cloud-fips

CloudNativePG barman-cloud plugin for PostgreSQL backup and recovery to S3-compatible 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/plugin-barman-cloud-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

The Chainguard plugin-barman-cloud-fips images are FIPS-hardened versions of the CloudNativePG barman-cloud plugin. This plugin provides PostgreSQL backup and recovery capabilities to S3-compatible storage using Barman Cloud tools with FIPS 140-2 compliant cryptographic operations.

FIPS 140-2 Compliance

The plugin-barman-cloud-fips Chainguard Image ships with a validated redistribution of the OpenSSL's FIPS provider module, ensuring all cryptographic operations used for backup encryption and S3 communication meet FIPS 140-2 standards. This includes:

• Backup encryption - All backup data is encrypted using FIPS-approved algorithms
• S3 communication - HTTPS connections to S3-compatible storage use FIPS-validated TLS
• Authentication - AWS credentials and authentication mechanisms comply with FIPS standards

For comprehensive information on FIPS support in Chainguard Images:

• FIPS-enabled Chainguard Images Guide
• FIPS 140-2 Standard Overview

The plugin consists of two components:

• Plugin Manager (plugin-barman-cloud-fips): Runs as a deployment and manages plugin lifecycle
• Sidecar (plugin-barman-cloud-sidecar-fips): Injected into PostgreSQL pods to handle backup operations

Getting Started

Using Chainguard's FIPS-Compliant CloudNative-PG Operator

Create a values-fips.yaml file to configure the CloudNative-PG operator with Chainguard FIPS images:

# values-fips.yaml for CloudNative-PG with Chainguard FIPS images
image:
  repository: cgr.dev/ORGANIZATION/cloudnative-pg-fips
  tag: latest
  pullPolicy: IfNotPresent

helm repo add cnpg https://cloudnative-pg.github.io/charts
helm repo update

# Install with Chainguard FIPS images
helm install cnpg cnpg/cloudnative-pg \
  --namespace cnpg-system \
  --create-namespace \
  --values values-fips.yaml

# Wait for operator to be ready
kubectl wait --for=condition=Available deployment/cnpg-cloudnative-pg -n cnpg-system --timeout=120s

# Verify the FIPS image is being used
kubectl get deployment cnpg-cloudnative-pg -n cnpg-system \
  -o jsonpath='{.spec.template.spec.containers[0].image}'

Download the plugin manifest and modify it to use Chainguard FIPS images:

# Set your custom FIPS images
PLUGIN_IMAGE="cgr.dev/ORGANIZATION/plugin-barman-cloud-fips:latest"
SIDECAR_IMAGE="cgr.dev/ORGANIZATION/plugin-barman-cloud-sidecar-fips:latest"

# Download and modify the manifest with yq to inject custom sidecar image
curl -fsSL "https://github.com/cloudnative-pg/plugin-barman-cloud/releases/download/v0.6.0/manifest.yaml" | \
  yq eval "select(.kind == \"Secret\") |= .data.SIDECAR_IMAGE = \"$(echo -n ${SIDECAR_IMAGE} | base64)\"" | \
  kubectl apply -f -

# Update the plugin operator deployment with custom FIPS image
kubectl set image deployment/barman-cloud "*=${PLUGIN_IMAGE}" -n cnpg-system
kubectl rollout status deployment barman-cloud -n cnpg-system --timeout=120s

Related FIPS Images

For complete PostgreSQL deployments with FIPS compliance, consider these related Chainguard FIPS images:

• postgresql-fips - FIPS-hardened PostgreSQL database
• cloudnative-pg-fips - FIPS-hardened CloudNativePG operator
• plugin-barman-cloud-sidecar-fips - FIPS-hardened sidecar component

Documentation and Resources

• FIPS-enabled Chainguard Images Guide - Complete guide to using FIPS images
• CloudNativePG Plugin Documentation
• Barman Cloud Plugin Repository
• CloudNativePG Backup and Recovery Guide

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.