Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpThe Azure Disk CSI driver enables the provisioning and management of Azure Disks through Kubernetes.This driver provides an interface for attaching, detaching, and managing persistent disks on Azure, helping applications achieve durable and high-performing storage.
Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.
This 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.
This guide outlines steps to test volume provisioning with the Azure Disk CSI driver. The Azure Disk CSI driver enables the provisioning and management of Azure Disks through Kubernetes.
To test the Azure Disk CSI driver, you need:
The Azure Disk CSI driver can be installed via Helm. Ensure you have the Helm repo added:
Then, install the driver with the following command, ensuring appropriate values are set in the configuration file:
If you face any issues with the above helm install, you might have to annotate the below
Annotate and label the CSI driver for Helm management:
Check that the CSI driver controller and node pods are running:
Create a StorageClass to provision disks using the Azure Disk CSI driver. This StorageClass should specify disk.csi.azure.com
as the provisioner.
Request a PersistentVolumeClaim using the Azure Disk StorageClass created in Step 1.
Verify the PVC has been created and is bound to a PersistentVolume (PV):
Example output:
Create a Pod that uses the PVC to test the volume's functionality. This Pod will write a test file to the mounted volume.
Verify that the Pod is created and enters the Running state:
Check that the data written by the Pod to the Azure Disk is successfully stored.
Expected output:
Check the logs of the Azure Disk CSI driver's controller and node pods to ensure that there are no errors during the volume provision and attachment process.
Once testing is complete, clean up the resources created:
If you installed the Azure Disk CSI driver with Helm and want to remove it:
If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.
Chainguard Images are a collection of container images designed for security and minimalism.
Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.
The main features of Chainguard Images include:
-dev
VariantsAs mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev
variant which does include a shell and package manager.
Although the -dev
image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev
variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.
That being said, it’s worth noting that -dev
variants of Chainguard Images are completely fine to run in production environments. After all, the -dev
variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.
To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
Apache-2.0
BSD-1-Clause
BSD-2-Clause
BSD-3-Clause
BSD-4-Clause-UC
CC-PDDC
GCC-exception-3.1
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs