Topic 2: Node Assignment
Official baseline: (The Kubernetes Authors, 2026). My working version: Node assignment is how workloads express where they can or should run.
Mental Model
Node assignment is how workloads express where they can or should run.
Notes
- Labels are the vocabulary of placement.
- Hard rules prevent placement; soft preferences shape placement.
- Topology spread is a reliability tool, not only a performance trick.
Homelab Angle
Label nodes by real traits: disk type, room, role, GPU, power domain.
Verify It
- Read the object status before changing the manifest.
- Check events for the controller or node that is actually complaining.
- Confirm the official source linked below still matches the cluster version you run.
Common Failure Modes
- Treating the YAML object as the system, instead of one input to a reconciliation loop.
- Debugging from outside the cluster when the failure only exists inside cluster networking or node state.
- Forgetting that Kubernetes version, addon version, and runtime behavior are linked.
Sources
- Assigning Pods to Nodes - source path:
content/en/docs/concepts/scheduling-eviction/assign-pod-node.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0. - Kubernetes documentation is licensed under CC BY 4.0; these notes are original commentary and link back to the official source.
The Kubernetes Authors. (2026). Assigning Pods to Nodes. https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/