Node Affinity
Definition
Node affinity determines preferred or mandatory placements in Kubernetes.
Kubernetes scheduling rules that place pods mandatorily or preferentially on certain nodes based on node labels.
Simply explained
An application should run on machines with suitable features, e.g., special computing hardware.
Why it matters in practice
Helps develop and operate digital systems robustly, securely, and maintainably.
Example from business
GPU workloads are placed on labeled nodes, other pods on standard nodes.
Limits and pitfalls
- Confusing requiredDuringSchedulingIgnoredDuringExecution and preferredDuringSchedulingIgnoredDuringExecution or ignoring taints, resources, topology, and failures.
Origin & history
Node Affinity extended simple Node Selector rules with more expressive conditions and preferences.
Use in mid-sized companies
- Possible application: GPU workloads are placed on labeled nodes, other pods on standard nodes.
Frequently asked questions
What does Kubernetes node affinity mean?
Kubernetes scheduling rules that place pods mandatorily or preferentially on certain nodes based on node labels.
Which mistakes should be avoided?
Confusing requiredDuringSchedulingIgnoredDuringExecution and preferredDuringSchedulingIgnoredDuringExecution or ignoring taints, resources, topology, and failures.
Sources
Source verified on 10.10.2026. Editorial application examples are hypothetical; no evidence of real customer results.
Editorially reviewed on: