dhi.io/azure-keyvault-controller
Azure Key Vault Controller
Kubernetes controller that synchronizes Azure Key Vault secrets, certificates, and keys into native Kubernetes Secrets via the AzureKeyVaultSecret CRD.
pushed 1 day ago
linux/amd64, linux/arm64
21.37 MB
for linux/amd64
135
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 Azure Key Vault Controller
Azure Key Vault Controller is the controller component of the akv2k8s project from Sparebanken
Vest. It watches AzureKeyVaultSecret custom resources and synchronizes the referenced secrets, certificates, and keys
from Azure Key Vault into native Kubernetes Secret objects, so workloads can consume them through envFrom,
secretKeyRef, or projected volumes without persisting Azure credentials in the cluster or running custom sync jobs.
Requires Kubernetes v1.16+.
For more details, see https://github.com/SparebankenVest/azure-key-vault-to-kubernetes.
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 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
Kubernetes® is a registered trademark of The Linux Foundation. Microsoft® and Azure® are registered trademarks of Microsoft Corporation. All rights in those marks are reserved to their respective owners. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.