From Static Tokens to Attestation: The Evolution of Secure Node Joining#

Ciprian Hacman & Jack Francis, Microsoft; Michael McCune & Josephine Pfeiffer, Red Hat; Justin Santa Barbara, Google

• Why: The framing is the right one: when Karpenter creates capacity in seconds and users plug custom nodes into managed control planes, "if the kubelet connects, it's in" is no longer a defensible trust model. This is the identity problem at the infrastructure layer.
• What: A cross-vendor panel — kOps and Cluster API maintainers plus engineers from the major cloud providers — on how node joining works today and how it should work.
• How: The stated scope is defining a root of trust, validating node identities with metadata and attestation, locking down CSR approval, binding joins to declarative objects, and post-join controls to limit privilege creep — NodeRestriction, scoped RBAC, admission, and drift detection.
• Where applicable: Broadly applicable, and unusually so for a security talk: the panel spans kOps, Cluster API and the managed offerings, so the answers should not be single-vendor. Most urgent for anyone letting nodes join from outside their own provisioning path.