Pod scheduling fails when requiredDuringSchedulingIgnoredDuringExecution affinity rules cannot be satisfied. No nodes match the required labels, node resources, or topology constraints.
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
Additional notes and platform-specific considerations.
Failed to connect to server: connection refused (HTTP/2)
How to fix "HTTP/2 connection refused" error in Kubernetes
missing request for cpu in container
How to fix "missing request for cpu in container" in Kubernetes HPA
error: invalid configuration
How to fix "error: invalid configuration" in Kubernetes
Fifth diagnostic step