Lab26 - Upgrading Kubernetes Cluster
Lab26 - Upgrading Kubernetes Cluster
Lab26 - Upgrading Kubernetes Cluster
Introduction:
Note: -
• All containers are restarted after upgrade, because the container spec hash value is changed.
• You only can upgrade from one MINOR version to the next MINOR version, or between PATCH
versions of the same MINOR. That is, you cannot skip MINOR versions when you upgrade. For
example, you can upgrade from 1.y to 1.y+1, but not from 1.y to 1.y+2
1. Ensure that you have logged-in as root user with password as linux on kube-master node.
1.1 Let us view kubeadm configuration file
# kubeadm version
Output:
# systemctl daemon-reload
# systemctl restart kubelet
Output:
Output:
# systemctl daemon-reload
# systemctl restart kubelet
3.7 Exit from the kube-node1
# exit
Output:
Output:
# systemctl daemon-reload
# systemctl restart kubelet
# exit