ceph-csi-operator-fips

Fips

Infra

Stig

Updated 4 days ago

Ceph-CSI-Operator-FIPS Overview

Secure your stack with a FIPS-validated, hardened Ceph-CSI-Operator image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

Ceph-CSI-Operator manages the deployment and lifecycle of the Ceph CSI drivers (RBD, CephFS, and NFS) on Kubernetes through a set of custom resources, replacing manual driver manifests with a declarative, operator-managed workflow. Use this image when you need to meet the requirements for FIPS-validated cryptographic protection.

FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

This guide installs the Ceph-CSI-Operator in a dedicated test or development cluster and deploys an RBD driver instance.

Prerequisites

A running Kubernetes cluster (v1.32 or higher is recommended)
Helm v3 (Installation instructions)
kubectl installed and configured

Step 1: Add Repository to your Local Client

Add the Helm chart to your local Helm client.

helm repo add ceph-csi-operator https://ceph.github.io/ceph-csi-operator/
helm repo update

Step 2: Render the Chart

Render the chart locally with the image overrides to confirm the Minimus image will be deployed:

helm template ceph-csi-operator \
  --set controllerManager.manager.image.repository=reg.mini.dev/ceph-csi-operator-fips \
  --set controllerManager.manager.image.tag=latest \
  ceph-csi-operator/ceph-csi-operator | grep "image:" | sort -u

Step 3: Deploy the Helm Chart

Install the operator into its own namespace:

helm install ceph-csi-operator \
  --set controllerManager.manager.image.repository=reg.mini.dev/ceph-csi-operator-fips \
  --set controllerManager.manager.image.tag=latest \
  --create-namespace --namespace ceph-csi-operator-system \
  ceph-csi-operator/ceph-csi-operator

Step 4: Verify

Wait a minute and check that the operator pod is up and running:

kubectl -n ceph-csi-operator-system get po

Confirm that the Minimus image was deployed:

kubectl -n ceph-csi-operator-system describe pods | grep Image:

Step 5: Create a Driver Resource

Deploy an RBD Driver custom resource to have the operator roll out the RBD CSI driver:

kubectl apply -f - <<EOF
apiVersion: csi.ceph.io/v1
kind: Driver
metadata:
  name: rbd.csi.ceph.com
  namespace: ceph-csi-operator-system
EOF

Confirm the driver pods were created by the operator:

kubectl -n ceph-csi-operator-system get po -l app.kubernetes.io/name=ceph-csi-operator

Clean Up

Uninstall the driver, the chart, and remove the namespace:

kubectl delete driver rbd.csi.ceph.com -n ceph-csi-operator-system
helm uninstall ceph-csi-operator -n ceph-csi-operator-system
kubectl delete ns ceph-csi-operator-system

Technical Considerations

The Ceph-CSI-Operator-FIPS image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image. The images are largely interchangeable, with a few differences as noted below.

Ceph-CSI-Operator-FIPS built by Minimus:

Runs as a non-root user by default for a security-first approach that protects against privilege escalation attacks.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.