Merge pull request #31996 from RA489/upgradenote

kubeadm-upgrade: add note about verifying the kubelet service status
This commit is contained in:
Kubernetes Prow Robot
2022-03-02 17:08:46 -08:00
committed by GitHub
@@ -43,6 +43,7 @@ first drain the node (or nodes) that you are upgrading. In the case of control p
they could be running CoreDNS Pods or other critical workloads. For more information see
[Draining nodes](/docs/tasks/administer-cluster/safely-drain-node/).
- All containers are restarted after upgrade, because the container spec hash value is changed.
- To verify that the kubelet service has successfully restarted after the kubelet has been upgraded, you can execute `systemctl status kubelet` or view the service logs with `journalctl -xeu kubelet`.
<!-- steps -->