Cert-Manager CSI Driver

Kubernetes CSI driver that requests and mounts cert-manager-issued X.509 certificates to pods while keeping private keys on the node.

  • Infrastructure
  • Security
  • Tools & Utilities
Kubernetes CSI driver that requests and mounts cert-manager-issued X.509 certificates to pods while keeping private keys on the node.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

72/100 Good

Maintained
100last commit 15 days ago
Popular
48248 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
94no serious findings, 1 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
248
Open issues
26
Last commit
2026-11-06
Latest release
v0.16.1
License
Apache-2.0
Activity
declining

Checked 14 days ago - source: GitHub (cert-manager/csi-driver)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install base cert-manager first Install cert-manager in your cluster before adding the CSI driver, because the CSI driver depends on cert-manager to create and renew certificates. Without cert-manager running, the driver has no certificates to expose, so certificate-dependent storage will not work. source
  • Helm: create namespace and enable CRDs If you install cert-manager with Helm (a package manager for Kubernetes), use the OCI chart command with --namespace cert-manager --create-namespace and --set crds.enabled=true. The flag installs the required CRDs (cluster instructions for cert-manager's Issuers and Certificates), so Kubernetes will accept those objects instead of failing. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do Pods mounting the CSI driver need a cert-manager Certificate resource?

No. Pods that mount the cert-manager csi-driver request certificates from cert-manager without needing a Certificate resource to be created.

Where does the CSI driver write mounted certificate data on the host?

It can be configured to write the key and certificate data from anywhere in the host file system, but by default it uses /tmp/cert-manager-csi. Each mounted volume gets its own directory inside that directory.

Is there a report of certificates being re-requested when a container restarts?

Yes, the GitHub issue tracker lists an issue titled 'Certificate is re-requested when container restarts'.

Answers sourced from cert-manager.io, cert-manager.io, github.com

Community

Collected 48 days ago - public community threads