HUB
Sign inSign up

readystack/kubernetesnode

By readystack

•Updated 1 day ago

Kubernetes Node: kubelet, containerd and CNI for a node. Signed; SBOM and SLSA v1 provenance.

Image
Integration & delivery
Developer tools
0

1.9K

readystack/kubernetesnode repository overview

⁠Kubernetes Node

Signed: cosign SBOM: SPDX attached Provenance: SLSA v1

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

Source, recipe and records

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-only; its source is in the kit) and the GNU C Library (LGPL-2.1-or-later; Debian's glibc 2.36-9+deb12u14 from the pinned builder image), both linked statically into runc, 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:6729b9738ef502f9333f29e6a00803e23e7c7d11cb5d70294cd874429760c385 on 2026-11-17.

  • 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/kubernetesnode⁠
  • ReadyStack release check — passed at release on 2026-11-17: 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:6729b9738ef502f9333f29e6a00803e23e7c7d11cb5d70294cd874429760c385; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/kubernetesnode:v1.36.6-CE-scratch-r3.
  • 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-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/kubernetesnode:v1.36.6-CE-scratch-r3

# ✗ 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-r3 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠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 a free download for any registered account at readystack.dev/products/kubernetesnode⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:065e7cccc0f87c9a7b957151a66c185ab45e10dcd639fb864496b71b01db49ad on 2026-11-17.

— ReadyStack · readystack.dev

Tag summary

Content type

Image

Digest

sha256:6729b9738…

Size

121.6 MB

Last updated

1 day ago

docker pull readystack/kubernetesnode:v1.36.6-CE-scratch-r3