readystack/kubernetesnode repository overview

⁠Kubernetes Node

readystack/kubernetesnode:v1.36.6-CE-scratch-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/kubernetesnode/recipe⁠
• Upstream source at this release's pinned commit (v1.36.6): https://github.com/kubernetes/kubernetes/tree/1b2171b110bb2a2542e1322035c6583ec86eb976⁠
• Also built from: github.com/containerd/containerd v2.3.7⁠, github.com/opencontainers/runc v1.5.2⁠, github.com/seccomp/libseccomp v2.6.1⁠, github.com/containernetworking/plugins v1.9.1⁠, github.com/kubernetes-sigs/cri-tools v1.36.0⁠, github.com/kubernetes/release master⁠
• Product page: https://readystack.dev/products/kubernetesnode⁠
• Hermetic Build Kit for this release: https://readystack.dev/buy.html?product=kubernetesnode⁠
• Release history (JSON): https://readystack.dev/api/releases/kubernetesnode⁠
• Defect record: https://readystack.dev/defects.html?product=kubernetesnode⁠
• Today's scan: https://readystack.dev/products/kubernetesnode#pp-grade⁠
• 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 kubernetes v1.36.6 containerd v2.3.7, runc v1.5.2 (with libseccomp 2.6.1), containernetworking/plugins v1.9.1, cri-tools v1.36.0 and kubernetes/release's package templates; all Apache-2.0 except libseccomp (LGPL-2.1, linked statically into runc; its source is in the kit), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Cluster administrators who add their own Linux servers to a Kubernetes cluster, for example with kubeadm.

Why: A Kubernetes node runs the kubelet, a container runtime and network plugins. The kubelet registers the machine with the control plane and makes sure the pods assigned to it are running.

Use case: A team adds new servers to an on-premises cluster. Each server gets the kubelet, a container runtime and the network plugins; kubeadm join registers it with the control plane, and from then on the scheduler can place pods there and the kubelet keeps them running.

About the upstream project, written from its own description: https://kubernetes.io/docs/concepts/architecture/nodes/⁠ · https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/⁠ · https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:665c06f34266e48226bb5321a05d403c960e0473f5cf8d6c58ef2e45be14bbaf on 2026-10-29.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/kubernetesnode⁠
• ReadyStack release check — passed at release on 2026-10-29: 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:665c06f34266e48226bb5321a05d403c960e0473f5cf8d6c58ef2e45be14bbaf; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/kubernetesnode:v1.36.6-CE-scratch-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (65534:65534).
• 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-scratch-r1 — the release on sale 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/kubernetesnode:v1.36.6-CE-scratch-r1

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

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

⁠Licences

Apache-2.0 AND LGPL-2.1-only AND LGPL-2.1-or-later. kubernetes, containerd, runc, the CNI plugins, cri-tools and the kubernetes/release templates are Apache-2.0. runc (static-pie, the only binary here that links C) links libseccomp 2.6.1 (LGPL-2.1-only) and the GNU C Library 2.36 (LGPL-2.1-or-later): Debian's glibc 2.36-9+deb12u14 (libc6-dev) from the pinned builder image golang:1.26.10-bookworm@sha256:632dff7351799a5a9954a48dc06670ade72ee44e8c351cdc0e5a57af2fea21af. libgcc (GCC 12.2.0, GPL-3.0-or-later WITH GCC-exception-3.1) is linked into runc too; its runtime library exception puts no licence condition on runc.

This image's org.opencontainers.image.licenses label says Apache-2.0 AND LGPL-2.1-only: it understates the licences, because it does not name glibc. The next revision of this image corrects the label and adds glibc's copyright file to /usr/local/share/kubernetesnode/licenses/. The image's SPDX document (/usr/local/share/readystack/sbom/runc.spdx.json) lists glibc (libc6-dev 2.36-9+deb12u14), libgcc and libseccomp.

Corresponding source: glibc, Debian's source package glibc 2.36-9+deb12u14 at https://snapshot.debian.org/package/glibc/2.36-9%2Bdeb12u14/⁠ (glibc_2.36-9+deb12u14.dsc, glibc_2.36.orig.tar.xz, glibc_2.36-9+deb12u14.debian.tar.xz); libseccomp, its release tarball, which the ReadyStack Hermetic Build Kit for this release carries (vendored/libseccomp). The kit also carries runc's source and the builder image whose libc.a was linked, so runc can be rebuilt and relinked offline.

⁠Deployment

Not a service: the files of a kubeadm node's host. The image's filesystem is the tree the Kubernetes VM Stack's install-node.sh installs (binaries in /usr/local/bin and /opt/cni/bin, systemd units in /etc/systemd/system, containerd and crictl configuration templates under /etc); the same tree is built as a tarball by BUILD_TARBALL.sh in the build kit. On the host, containerd and kubelet run under systemd as root; kubeadm init/join then starts the control plane and the node's Pods from images in the local registry.

sudo ./install-node.sh --tarball kubernetesnode-v1.36.6-linux-amd64.tar.gz --registry-config /root/registry.env

⁠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 at readystack.dev/buy.html⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:0a264881a0b7357fb20767b0922661bf4ba4423b3e90e595195bf18748a8d79c on 2026-10-29.

— ReadyStack · readystack.dev