dhi.io/vault-csi-provider
Vault CSI Provider
vault-csi-provider is HashiCorp's official Kubernetes integration that securely mounts Vault secrets as files in pod containers using the Container Storage Interface, enabling applications to access centralized secrets without code changes or embedded credentials.
pushed 1 day ago
linux/amd64, linux/arm64
47.84 MB
for linux/amd64
165
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About vault-csi-provider
vault-csi-provider is HashiCorp's official Kubernetes integration that enables secure, file-based access to Vault
secrets through the Container Storage Interface (CSI). It operates as a provider plugin for the Secrets Store CSI
driver, allowing Kubernetes pods to mount secrets from HashiCorp Vault directly as files in their filesystem without
requiring code changes or embedded credentials in container images.
The system works by intercepting pod mount requests through SecretProviderClass resources, authenticating with Vault using Kubernetes service account tokens, and dynamically retrieving secrets that are then mounted as files within pod containers. This approach supports various Vault secret engines including key-value stores, dynamic database credentials, PKI certificates, and custom secret backends, while maintaining secure authentication through Vault's Kubernetes auth method.
This integration allows organizations to centralize secret management through Vault while preserving Kubernetes-native deployment patterns, supporting use cases like dynamic credential rotation, certificate lifecycle management, and zero-trust application security across development and production environments without the overhead of sidecar containers or init processes.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
This listing is prepared by Docker. All third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.