After finishing a kubeadm upgrade, budget analytics operators must confirm components moved forward. Which verification approach best matches admin practice?
Select an answer to reveal the explanation.
Short Explanation
When the upgrade party ends, you still check name tags—are apiserver, kubelet, and friends actually on the version you paid for? kubectl version and a glance at node/control-plane versions tell you if something got stuck mid-flight. “No crashing Pods” is nice, but it’s not a version audit.
Full Explanation
Post-upgrade verification confirms kube-apiserver, controller-manager, scheduler, etcd images, and node kubelets match the intended release within skew. kubectl version and kubectl get nodes (or describing control-plane static pod images) provide that evidence. Skipping version checks can leave mixed minors unnoticed.