dhi.io/spiffe-csi-driver
SPIFFE CSI Driver
Kubernetes CSI driver that injects the SPIFFE Workload API socket into workload pods as an ephemeral inline volume.
pushed 2 days ago
linux/amd64, linux/arm64
31.99 MB
for linux/amd64
110
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 SPIFFE CSI Driver
The SPIFFE CSI Driver is a
Container Storage Interface (CSI) driver for
Kubernetes that facilitates injection of the SPIFFE Workload API socket into workload pods as an ephemeral inline
volume. The SPIFFE Workload API is served over a Unix domain socket; implementations such as
SPIRE rely on DaemonSets to run one Workload API server instance per node. The
primary motivation for using a CSI driver is to avoid the use of hostPath volumes in workload containers, which is
commonly disallowed or restricted by policy due to inherent security concerns.
The driver mounts a directory containing the SPIFFE Workload API socket — provided by a SPIFFE implementation such as
SPIRE — as a read-only bind mount into workload pods at the requested target path. When a pod declares an ephemeral
inline volume using this driver, the driver is invoked to perform the bind mount; when the pod is destroyed, the driver
removes it. This lifecycle management ensures workloads always have access to a valid Workload API socket without
requiring elevated privileges or direct hostPath access in the workload containers themselves.
The SPIFFE CSI Driver is typically deployed as a container in the same DaemonSet that runs the SPIRE Agent, registered
with the kubelet using the CSI Node Driver Registrar sidecar. CSI Ephemeral Inline Volumes require at least Kubernetes
1.15 (via the CSIInlineVolume feature gate) or Kubernetes 1.16 and later where the feature is enabled by default. The
project is currently in the
pre-production phase of the SPIFFE maturity
model.
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
Spiffe® is a registered trademark of the Linux Foundation. All rights in the mark are reserved to the Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.
Kubernetes® is a registered trademark of the Linux Foundation. All rights in the mark are reserved to the Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.