Chainguard Container for secrets-store-csi-driver-provider-azure

Azure Key Vault provider for Secret Store CSI driver allows you to get secret contents stored in Azure Key Vault instance and use the Secret Store CSI driver interface to mount them into Kubernetes pods.

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/secrets-store-csi-driver-provider-azure: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 secrets-store-csi-driver-provider-azure container image is comparable to Microsoft's Azure CSI driver. Chainguard's image contains only the minimum set of dependencies needed to run the driver.

Getting Started

The official documentation outlines how to set up the Azure provider for Secrets Store CSI Driver. To get started with Chainguard's secrets-store-csi-drive-provider-azure image, create a custom values.yaml file for the Helm release:

linux:
  image:
    repository: "cgr.dev/<ORGANISATION>/secrets-store-csi-driver-provider-azure"
    tag: "latest"

Add the Helm chart and install the csi-secrets-store-provider-azure release:

helm repo add csi-secrets-store-provider-azure https://azure.github.io/secrets-store-csi-driver-provider-azure/charts
helm install csi-secrets-provider csi-secrets-store-provider-azure/csi-secrets-store-provider-azure -f custom_values.yaml

This can now be tested by creating a Secrets Provider Class Object. The following is an example manifest:

apiVersion: secrets-store.csi.x-k8s.io/v1
kind: SecretProviderClass
metadata:
  name: azure-secrets
  namespace: kube-system
spec:
  provider: azure
  parameters:
    usePodIdentity: "false"
    useVMManagedIdentity: "true"              
    keyvaultName: <KEY VAULT NAME>
    cloudName: ""
    objects:  |
      array:
        - |
          objectName: <SECRET NAME>
          objectType: secret # object types: secret, key or cert
          objectVersion: ""                    
    tenantId: "<TENANT ID>"

The secret is consumed by a Kubernetes Pod. In this example, the Azure secret from a Key Vault Secret is mounted to /mnt/secret-store:

kind: Pod
apiVersion: v1
metadata:
  name: demo-pod
  namespace: kube-system
spec:
  containers:
    - name: nginx
      image: cgr.dev/<ORGANISATION>/busybox:latest
      command: ["/bin/sh", "-c", "sleep 864000"]
      volumeMounts:
      - name: secrets-store01-inline
        mountPath: "/mnt/secrets-store"
        readOnly: true
  volumes:
    - name: secrets-store01-inline
      csi:
        driver: secrets-store.csi.k8s.io
        readOnly: true
        volumeAttributes:
          secretProviderClass: <KEY VAULT NAME>
        nodePublishSecretRef: # Kubernetes secret that contains details used to authenticate to Azure
          name: "sscdp-azure-settings"

Documentation and Resources

• Configuring Azure secrets provider
• Azure Driver Helm Charts
• Azure Driver Github

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.