Court-records pods stay Pending because their nodeSelector requires a label the target nodes do not have. Nodes themselves are Ready. How should this be classified?
Select an answer to reveal the explanation.
Short Explanation
The nodes are fine; the pods are picky. Wrong or missing labels mean the scheduler finds zero matches and leaves them Pending.
Full Explanation
Pods with nodeSelector or affinity constraints remain Pending when no Ready node satisfies those rules. That is a scheduling constraint problem, not evidence that nodes are NotReady, that a PVC cannot provision, or that CoreDNS is crash-looping—unless separate symptoms show those faults.