dhi.io/kube-scheduler
Kubernetes Scheduler (kube-scheduler)
Schedules pods onto nodes. kube-scheduler watches for newly created pods with no assigned node, and selects a node for them to run on.
pushed 12 hours ago
linux/amd64, linux/arm64
61.52 MB
for linux/amd64
203
for linux/amd64
Active support
until Jun 2027
-
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 Kubernetes Scheduler (kube-scheduler)
kube-scheduler assigns newly created Pods to nodes. It watches for Pods without a scheduled node, evaluates node feasibility and scoring (including taints/tolerations, affinities, and resource constraints), and binds Pods to the selected node.
Use this image when you need a hardened, minimal container image for running the Kubernetes scheduler as part of a Kubernetes control plane deployment.
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
Kubernetes® is a registered trademark of The Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.