A school district upgrades kubelet on a worker while keeping applications available. Which node lifecycle pattern matches standard practice?
Select an answer to reveal the explanation.
Short Explanation
Patching a worker is like closing one checkout lane—you stop new customers, clear the line, fix the register, then reopen. Cordon and drain, upgrade kubelet, make sure the node is healthy, then uncordon. Skipping drain means Pods sit on a node mid-surgery.
Full Explanation
Worker upgrades typically mark the node unschedulable (cordon), evacuate Pods (drain), upgrade kubelet packages, confirm Ready status, then uncordon. That sequence limits disruption when Deployments have spare replicas on other nodes. Upgrading without drain risks breaking in-place workloads during kubelet restart.