Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpThis driver allows Kubernetes to access an NFS server running on a Linux node.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
Chainguard's kubernetes-csi-driver-nfs Image is comparable to the official nfsplugin
Image from Docker Hub. However, the Chainguard image contains only the minimum set of tools and dependencies needed to function. This means it doesn't include things like a shell or a package manager.
If you already have an NFS server setup, you can skip this step.
If you don't have an existing NFS server setup, you can use the following YAML to get a minimal nfs-server setup up and running. Note that this is not a production setup, and is just meant to test the Chainguard image:
This YAML will set up a server to expose the other server and deployment that run the server pod.
In this section you will use the Helm chart available from the NFS CSI driver for Kubernetes GitHub repository. This will enable Kubernetes to handle NFS volumes:
Say you want to tell Kubernetes how to provision storage using NFS. To do this, you'll first need to retrieve the NFS server's clusterIP
:
Next, you would create a storage class that tells Kubernetes to use the NFS server for storage:
Following that, create a Persistent Volume Claim (PVC) that will request storage from the storage class:
To test that this setup will work, create a pod that uses the PVC:
Finally, check whether the pod was created and in a Ready
state:
This will confirm the csi-driver was able to provision a persistent volume for the pod and that the csi-driver is working as expected.
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:
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.
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.
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.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
AFL-2.1
Apache-2.0
Artistic-1.0-Perl
BSD-1-Clause
BSD-2-Clause
BSD-3-Clause
BSD-4-Clause-UC
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.