A county must upgrade a kubeadm cluster from an N-2 minor release toward the current supported minor. Which upgrade ordering principle should platform ops follow?
Select an answer to reveal the explanation.
Short Explanation
Cluster upgrades are like remodeling the front desk before the warehouse—the brains have to move first within the rules. Bring the control plane forward with kubeadm’s documented steps, then roll the workers, and stay inside Kubernetes’ supported skew. Flipping workers ahead of the API is how you invent mystery bugs.
Full Explanation
Kubernetes documents version skew limits between kube-apiserver and kubelets. kubeadm upgrade workflows advance the control plane first, then upgrade worker kubelets within supported skew. Upgrading workers ahead of the API server risks unsupported skew and broken node registration.