Chainguard Container for kubernetes-csi-external-snapshotter-fips

Sidecar container that watches Kubernetes Snapshot CRD objects and triggers CreateSnapshot/DeleteSnapshot against a CSI endpoint. This container image includes the snapshotter, snapshot-controller and snapshot-validation-webhook.

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/kubernetes-csi-external-snapshotter-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

Chainguard's kubernetes-csi-external-snapshotter-fips container image collection is a drop-in replacement for the following images:

• k8s.gcr.io/sig-storage/csi-snapshotter
• k8s.gcr.io/sig-storage/snapshot-controller
• k8s.gcr.io/sig-storage/snapshot-validation-webhook

Chainguard Container Images are designed with minimalism and security in mind, and thus the kubernetes-csi-external-snapshotter-fips image has the following differences from the upstream image:

• We set the entrypoints to usr/bin/{component}, where as the upstream sets it to /{component}.

FIPS Support

The kubernetes-csi-external-snapshotter-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

Getting Started

Snapshotter

To deploy the snapshotter, apply the manifests found in the upstream project here. You'll need to adjust the image to use cgr.dev/ORGANIZATION/kubernetes-csi-external-snapshotter-fips instead. You can do this by extending the existing kustomization file as follows:

# ...
images:
  - name: registry.k8s.io/sig-storage/csi-snapshotter
    newName: cgr.dev/ORGANIZATION/kubernetes-csi-external-snapshotter-fips
    digest: <insert image digest>

Snapshot Controller

To deploy the snapshotter, apply the manifests found in the upstream project here. You'll need to adjust the image to use cgr.dev/ORGANIZATION/kubernetes-csi-external-snapshot-controller-fips instead. You can do this by extending the existing kustomization file as follows:

# ...
images:
  - name: registry.k8s.io/sig-storage/snapshot-controller
    newName: cgr.dev/ORGANIZATION/kubernetes-csi-external-snapshot-controller-fips
    digest: <insert image digest>

Validation Webhook

As of Feb 2025, upstream looks to have deleted 'snapshot-validation-webhook' from the main branch. It still exists in the latest git release at this time: v8.1.11. It's likely this image will be depreciated in a future release.

To deploy the webhook, see the documentation in the upstream project. You'll just need to replace the container spec's image value with cgr.dev/ORGANIZATION/kubernetes-csi-external-snapshot-validation-webhook-fips.

You can verify that the webhook is working by following these instructions to submit an invalid snapshot definition and see whether it gets rejected.

Once all the components are deployed, we can try to apply one valid and one invalid snapshot to check the behaviour.

Apply the below invalid Snapshot, this should be rejected by the validating webhook.

apiVersion: snapshot.storage.k8s.io/v1
kind: VolumeSnapshot
metadata:
  name: new-snapshot-demo-v1
spec:
  volumeSnapshotClassName: csi-hostpath-snapclass-v1
  source: # Only one of the two fields should be set for a snapshot. Therefore this snapshot is invalid.
    persistentVolumeClaimName: pvc 
    volumeSnapshotContentName: vsc

We can then try to apply the below valid Snapshot which should be allowed by the validating webhook.

apiVersion: snapshot.storage.k8s.io/v1
kind: VolumeSnapshot
metadata:
  name: new-snapshot-demo-v1
spec:
  volumeSnapshotClassName: csi-hostpath-snapclass-v1
  source:
    persistentVolumeClaimName: hpvc

Documentation and Resources

• Official Usage Guide
• Example Configs

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.