readystack/kubescheduler repository overview

⁠kube-scheduler

readystack/kubescheduler:v1.36.6-CE-ubuntu24.04-r3

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/kubescheduler/recipe⁠
• Upstream source at this release's pinned commit (v1.36.6): https://github.com/kubernetes/kubernetes/tree/1b2171b110bb2a2542e1322035c6583ec86eb976⁠
• Product page: https://readystack.dev/products/kubescheduler⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/kubescheduler⁠
• Release history (JSON): https://readystack.dev/api/releases/kubescheduler⁠
• Defect record: https://readystack.dev/defects.html?product=kubescheduler⁠
• Today's scan: https://readystack.dev/products/kubescheduler#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=kubescheduler⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠
• Part of the Kubernetes VM Stack: https://readystack.dev/stacks/kubernetes-vm-stack⁠

A cosign-signed build of kube-scheduler v1.36.6 from Kubernetes (github.com/kubernetes/kubernetes, tag v1.36.6, commit 1b2171b110bb2a2542e1322035c6583ec86eb976), Apache-2.0, built from source on Go 1.26.10, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Cluster administrators and platform engineers who build and run their own Kubernetes control plane.

Why: kube-scheduler decides where each new pod runs. It filters out nodes that cannot run the pod, scores the rest against resources and constraints such as affinity, and binds the pod to the highest-scoring node.

Use case: A team deploys a memory-hungry service whose replicas must not share a node. kube-scheduler skips nodes without enough free memory, honours the anti-affinity rule and places each replica on a different suitable node; if no node fits, the pod waits until one does.

About the upstream project, written from its own description: https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/⁠ · https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:f2bbe05f998e85280638e6e198532234602a247497225243994d7dd108b8c49f on 2026-11-12.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/kubescheduler⁠
• ReadyStack release check — passed at release on 2026-11-12: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:f2bbe05f998e85280638e6e198532234602a247497225243994d7dd108b8c49f; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/kubescheduler:v1.36.6-CE-ubuntu24.04-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (999:999).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.36.6-CE-ubuntu24.04-r3 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/kubescheduler:v1.36.6-CE-ubuntu24.04-r3

# ✗ unsupported (do not pull)
docker pull readystack/kubescheduler:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/kubescheduler:v1.36.6-CE-ubuntu24.04-r3 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

One binary per image, as upstream's images: /usr/local/bin/kube-scheduler, started by kubeadm's static Pod manifest /etc/kubernetes/manifests/kube-scheduler.yaml (command: kube-scheduler --kubeconfig=/etc/kubernetes/scheduler.conf ...). The ENTRYPOINT is /go-runner (upstream's kube-log-runner); a Pod command replaces it. In the Kubernetes VM Stack it is mirrored into the local registry as <LOCAL_REGISTRY>/kube-scheduler:v1.36.6 and kubeadm pulls it from there.

docker run --rm readystack/kubescheduler:v1.36.6-CE-ubuntu24.04-r3 kube-scheduler --version

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/kubescheduler⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:611ee0ead3de426c8ce2fe66ce500aabcd314a31f580656434389b186d40dc99 on 2026-11-12.

— ReadyStack · readystack.dev