cass-config-builder-fips

Chainguard Container for cass-config-builder-fips

FIPS-enabled minimal cass-config-builder container image for K8ssandra deployments.

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/cass-config-builder-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 cass-config-builder and is designed for use with K8ssandra deployments. It functions as a drop-in replacement for the non-FIPS cass-config-builder image in environments requiring FIPS 140-3 compliance.

The image runs as a non-root user:

uid=65532(nonroot) gid=65532(nonroot) groups=65532(nonroot)

FIPS Support

The cass-config-builder-fips Chainguard Image ships with:

• A validated redistribution of OpenSSL's FIPS provider module
• BouncyCastle FIPS (BC-FIPS) cryptographic provider for Java
• BouncyCastle TLS FIPS provider for SSL/TLS support

For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

The image includes FIPS-related environment variables pre-configured:

Getting Started

This image is used as an init container by the K8ssandra operator to generate Cassandra configuration files. To use this image, follow the official documentation for installing the K8ssandra Operator Helm Chart.

In the ImageConfiguration section, configure K8ssandra to use this FIPS-enabled image for the cass-config-builder component:

apiVersion: config.k8ssandra.io/v1beta1
kind: ImageConfig
metadata:
  name: image-config
images:
  config-builder: "cgr.dev/ORGANIZATION/cass-config-builder-fips:latest"

After applying the ImageConfig, you may need to restart pods in the k8ssandra-operator namespace for changes to take effect.

To verify the image is working correctly, create a K8ssandraCluster resource:

apiVersion: k8ssandra.io/v1alpha1
kind: K8ssandraCluster
metadata:
  name: demo
  namespace: k8ssandra-operator
spec:
  cassandra:
    serverVersion: "4.0.1"
    datacenters:
      - metadata:
          name: dc1
        size: 3
        storageConfig:
          cassandraDataVolumeClaimSpec:
            storageClassName: standard
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 5Gi
        config:
          jvmOptions:
            heapSize: 512M

After creating the cluster, verify that pods are starting successfully. The cass-config-builder-fips image runs as an init container, so successful pod startup confirms the image is functioning correctly.

Documentation and Resources

• K8ssandra Documentation
• cass-config-builder GitHub
• K8ssandra Image Configuration
• FIPS-enabled Chainguard Images 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.