Pod scheduling fails when requiredDuringSchedulingIgnoredDuringExecution affinity rules cannot be satisfied. No nodes match the required labels, node resources, or topology constraints.
Fixes Pod failed to schedule: node(s) did not match pod hard affinity requirements
# Pod failed to schedule: node(s) did not match pod hard affinity requirementsPod failed to schedule: node(s) did not match pod hard affinity requirements
On this page
Hard affinity rules (requiredDuringSchedulingIgnoredDuringExecution) are mandatory constraints for pod scheduling. When no nodes match these rules, Kubernetes cannot schedule the pod. This error indicates a mismatch between pod affinity requirements and available cluster resources. Common causes include missing node labels, resource constraints, or topology misconfigurations.
First diagnostic step
Second diagnostic step
Third diagnostic step
Fourth diagnostic step
Fifth diagnostic step
Additional notes and platform-specific considerations.