A school-district node remains Ready but is cordoned. Why do new pods refuse to schedule there?
Select an answer to reveal the explanation.
Short Explanation
Cordon hangs a “no new guests” sign on a still-healthy house. The node can stay Ready—it just won’t take new pods.
Full Explanation
kubectl cordon sets spec.unschedulable so the scheduler skips the node (often shown as SchedulingDisabled). Existing pods may continue; Ready can remain true. Cordon does not delete the node object, does not by itself imply NoExecute eviction of all pods, and does not flip Ready solely by disabling scheduling.