dhi.io/vpa-admission-controller
Vertical Pod Autoscaler Admission Controller
Admission webhook controller for Kubernetes Vertical Pod Autoscaler that sets resource requests on new pods.
pushed 12 hours ago
linux/amd64, linux/arm64
17.25 MB
for linux/amd64
84
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 Vertical Pod Autoscaler Admission Controller
The Kubernetes Vertical Pod Autoscaler (VPA) Admission Controller is a critical component of the VPA system that runs as a mutating webhook in Kubernetes clusters. It intercepts pod creation and update requests to automatically set or modify CPU and memory resource requests based on recommendations from the VPA Recommender. As part of the three-component VPA architecture (Recommender, Updater, and Admission Controller), it ensures that new pods are created with optimal resource requests without requiring manual intervention or pod restarts, enabling efficient resource utilization and preventing resource starvation or waste in containerized workloads.
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. 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.