An HR cluster accidentally applies a NoSchedule taint to every worker. What is the expected scheduling symptom?
Select an answer to reveal the explanation.
Short Explanation
NoSchedule is a bouncer at the door. Without a matching toleration, new pods wait outside (Pending) even though the nodes still look Ready.
Full Explanation
A NoSchedule taint prevents the scheduler from placing pods that lack a matching toleration. If every worker is tainted, unschedulable pods stay Pending while nodes may still be Ready. NoSchedule does not by itself immediately delete all running pods (NoExecute is the eviction-oriented effect), is not limited to Ingress, and does not flip Ready solely by existing.