Chainguard Container for azurefile-csi-fips

This driver allows Kubernetes to access Azure File volume using smb and nfs protocols, csi plugin name: file.csi.azure.com.

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/azurefile-csi-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 comparable to the azurefile-csi image available from the Microsoft Artifact Registry. Switching to the Chainguard image should not require any changes to your existing setup.

FIPS support

Chainguard's azurefile-csi-fips images ship with a validated redistribution of the OpenSSL FIPS provider module. For more on FIPS support in Chainguard container images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

Getting Started

Kubernetes

You can follow the official documentation for running azurefile-csi on Kubernetes to run azurefile-csi.

Set the image on the Deployment and Daemonset:

$ kubectl set image -n kube-system deployment/csi-azurefile-controller azurefile=cgr.dev/ORGANIZATION/azurefile-csi-fips:latest
deployment.apps/csi-azurefile-controller image updated
$ kubectl set image -n kube-system daemonset/csi-azurefile-node azurefile=cgr.dev/ORGANIZATION/azurefile-csi-fips:latest
daemonset.apps/csi-azurefile-node image updated

Helm

You can use the official azurefile-csi-driver Helm chart to install the azurefile-csi-driver, replacing the azurefile image in values.yaml with the Chainguard image.

Use the following values.yaml file to configure the Helm chart:

image:
  azurefile:
    repository: cgr.dev/ORGANIZATION/azurefile-csi-fips
    tag: latest

Add the azurefile-csi-driver chart:

$ helm repo add azurefile-csi-driver https://raw.githubusercontent.com/kubernetes-sigs/azurefile-csi-driver/master/charts
"azurefile-csi-driver" has been added to your repositories

Install the azurefile-csi-driver chart with your custom values.yaml file:

$ helm install azurefile-csi azurefile-csi-driver/azurefile-csi-driver --values values.yaml
NAME: my-azurefile-csi-driver
LAST DEPLOYED: <DATE>
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
The Azure File CSI Driver is getting deployed to your cluster.

To check Azure File CSI Driver pods status, please run:

  kubectl --namespace=default get pods --selector="app.kubernetes.io/name=my-azurefile-csi-driver" --watch

Documentation and Resources

• Official azurefile-csi repository.
• Use Azure Files Container Storage Interface (CSI) driver in Azure Kubernetes Service (AKS)

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.