1. Images & Charts
  2. secrets-store-csi-driver
secrets-store-csi-driver

secrets-store-csi-driver

Infra
Updated 2 days ago

Secrets-Store-CSI-Driver Overview

Secure your stack with a hardened Secrets-Store-CSI-Driver image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.


The Secrets Store CSI Driver lets Kubernetes pods mount secrets, keys, and certificates from an external secret store as a volume, through the SecretProviderClass custom resource. Pairing it with a provider plugin for Azure Key Vault, AWS Secrets Manager, Google Cloud Secret Manager, or HashiCorp Vault keeps credentials out of environment variables and Kubernetes Secrets while centralizing where they're actually stored and rotated.


Try It Out

Prerequisites

  • A running Kubernetes cluster (v1.21 or higher is recommended)
  • Helm v3 (Installation instructions)
  • kubectl installed and configured

Step 1: Add Repository to your Local Client

helm repo add secrets-store-csi-driver https://kubernetes-sigs.github.io/secrets-store-csi-driver/charts
helm repo update

Step 2: Deploy via Helm Chart

Deploy the driver using the Minimus image:

helm install csi-secrets-store secrets-store-csi-driver/secrets-store-csi-driver \
    --namespace kube-system \
    --set linux.image.repository=reg.mini.dev/secrets-store-csi-driver \
    --set linux.image.tag=latest

Confirm the driver Pods are running:

kubectl -n kube-system get pods -l app=secrets-store-csi-driver

Step 3: Verify the CRDs were Installed

kubectl get crd | grep secrets-store.csi.x-k8s.io
NAME                                                        CREATED AT
secretproviderclasses.secrets-store.csi.x-k8s.io            2024-01-01T00:00:00Z
secretproviderclasspodstatuses.secrets-store.csi.x-k8s.io   2024-01-01T00:00:00Z

Mounting an actual secret requires a provider plugin registered alongside the driver — see the Azure, AWS, and Vault provider images in this catalog for a full walkthrough with a SecretProviderClass and a test pod.

Step 4: Clean Up

helm uninstall csi-secrets-store -n kube-system

Technical Considerations

The Secrets-Store-CSI-Driver image provided by Minimus is a slim, security-hardened alternative to the public image. The images are largely interchangeable, with a few differences as noted below.

Secrets-Store-CSI-Driver built by Minimus:

  1. Runs as root to support required functions in alignment with the public image.
  2. Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.


Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.