This content originally appeared on DEV Community and was authored by Sina Tavakkol
Day 34/40
Step-By-Step Guide To Upgrade a Multi Node Kubernetes Cluster With Kubeadm
Video Link
@piyushsachdeva
Git Repository
My Git Repo
In this section, the kubernetes cluster wil be update with kubeadm.
Let's assume we have 1 controller-plane with 3 worker nodes, and one is failed for a reason.
(Photo from the video)
node worker1 drain
then
-
workloadswould be evicted. -
nodeiscordonand unschedulable. - The
nginxpod will schedule in othernodebecause it's controlled bydeployment - The
mysqlpod and its data and configurations is gone.
If we replace or resolve the issues the failed node, we need to uncordon it to make it shcedulable and ready again.
It will accept new workload but not current workload.
(Photo from the video)
For upgrading we cannot skip the minor version and for upgrading we need to upgrade to one next minor version.
For example,at first upgrade 1.28.2 to 1.29.3, then we can upgrade from 1.29.3 to 1.30.2 and so on.
(Photo from the video)
As a kubernetes cluster admin, every month or every couple of months, we need to upgrade the cluster, that's why it's important concept for administration.
Note at single time, kubernetes only support last 3 minor versions. It means, no new bug fixes or updating the features on that minor version.
Example:
kube-apiserver is at
1.31
kubelet is supported at1.31,1.30,1.29, and1.28
source
Official document for upgrading with kubeadm, here
The upgrade workflow at high level is the following:
Upgrade a primary control plane node.
Upgrade additional control plane nodes.
Upgrade worker nodes.
Upgrading strategies:
- All at once, we have downtime.
- Rolling update, one by one.
- Blue Green, upgrading new cluster and transfer workloads from old one.
Upgrade Master node
Changing the package repository
hereDetermine which version to upgrade to
# Find the latest 1.31 version in the list.
# It should look like 1.31.x-*, where x is the latest patch.
sudo apt update
sudo apt-cache madison kubeadm
- Upgrading control plane nodes
# replace x in 1.31.x-* with the latest patch version
sudo apt-mark unhold kubeadm && \
sudo apt-get update && sudo apt-get install -y kubeadm='1.31.x-*' && \
sudo apt-mark hold kubeadm
kubeadm version
- Check the upgrade plan
kubeadm upgrade plan
(Photo from the video)
kubeadm upgrade apply v1.30.2
- Drain the node
kubectl drain <node-to-drain> --ignore-daemonsets
- Upgrade kubelet and kubectl
# replace x in 1.31.x-* with the latest patch version
sudo apt-mark unhold kubelet kubectl && \
sudo apt-get update && sudo apt-get install -y kubelet='1.31.x-*' kubectl='1.31.x-*' && \
sudo apt-mark hold kubelet kubectl
sudo systemctl daemon-reload
sudo systemctl restart kubelet
- Uncordon the node
# replace <node-to-uncordon> with the name of your node
kubectl uncordon <node-to-uncordon>
(Photos from the video)
Upgrade worker nodes
How it works
kubeadm upgrade apply does the following:
Checks that your cluster is in an upgradeable state:
The API server is reachable
All nodes are in the Ready state
The control plane is healthy
Enforces the version skew policies.
Makes sure the control plane images are available or available to pull to the machine.
Generates replacements and/or uses user supplied overwrites if component configs require version upgrades.
Upgrades the control plane components or rollbacks if any of them fails to come up.
Applies the new CoreDNS and kube-proxy manifests and makes sure that all necessary RBAC rules are created.
Creates new certificate and key files of the API server and backs up old files if they're about to expire in 180 days.
kubeadm upgrade node does the following on additional control plane nodes:
Fetches the kubeadm ClusterConfiguration from the cluster.
Optionally backups the kube-apiserver certificate.
Upgrades the static Pod manifests for the control plane components.
Upgrades the kubelet configuration for this node.
kubeadm upgrade node does the following on worker nodes:
Fetches the kubeadm ClusterConfiguration from the cluster.
Upgrades the kubelet configuration for this node.
- Upgrade kubeadm
# replace x in 1.31.x-* with the latest patch version
sudo apt-mark unhold kubeadm && \
sudo apt-get update && sudo apt-get install -y kubeadm='1.31.x-*' && \
sudo apt-mark hold kubeadm
- Call "kubeadm upgrade"
sudo kubeadm upgrade node
- Drain the node
# execute this command on a control plane node
# replace <node-to-drain> with the name of your node you are draining
kubectl drain <node-to-drain> --ignore-daemonsets
- Upgrade kubelet and kubectl
# replace x in 1.31.x-* with the latest patch version
sudo apt-mark unhold kubelet kubectl && \
sudo apt-get update && sudo apt-get install -y kubelet='1.31.x-*' kubectl='1.31.x-*' && \
sudo apt-mark hold kubelet kubectl
sudo systemctl daemon-reload
sudo systemctl restart kubelet
- Uncordon the node
# execute this command on a control plane node
# replace <node-to-uncordon> with the name of your node
kubectl uncordon <node-to-uncordon>
Summary
(Photo from the video)
This content originally appeared on DEV Community and was authored by Sina Tavakkol
Sina Tavakkol | Sciencx (2024-09-05T20:05:02+00:00) 40 Days Of Kubernetes (34/40). Retrieved from https://www.scien.cx/2024/09/05/40-days-of-kubernetes-34-40/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.