Hello,
The exercise says to upgrade to v 1.31.0 but I do not see it in the output of the first commands from the k8s docs - Upgrading kubeadm clusters | Kubernetes
How can I proceed? Thanks
Hi @Mundofik,
The screenshot you shared is for installing kubeadm tool. You will see the cluster version when you run the kubeadm upgrade plan.
Regards,
Hello @Tej-Singh-Rana , the screenshots I am sharing are for upgrading kubeadm, as per the instructions on the k8s page
kubeadm upgrade plan comes after, please see the steps in the official k8s docs:
First I have to find the version to upgrade to, which is 1.31.0 in the exercise. But such version is not shown in the output, as per my screenshot above.
So what is the next step here, to see the options for 1.31.0? Thanks
Hi @Mundofik ,
You need to read the question again. The question states to upgrade the Kubernetes version from v1.30.0 to v1.31.0. Which you’ll see once you install version 1.31 of kubeadm.
Reference:
After that, you’ll see the 1.31 version.
Please give it a try, let me know.
Hello @Tej-Singh-Rana thank you.
It works now after I changed the repo. I thought that since the old repo is deprecated, the new ones are already set by default.
I have an extra question. The step to drain the node for controlplane
is it done only when the control planes act as both control and worker nodes, right?
If the control planes do not have any pod running we can skip draining and uncordoning them or …?
Thanks
In our labs, we’ll always have things set up so that there are at least two nodes that can take workloads, so this won’t be a problem there. In a production environment, this of course would be a problem, since an upgrade would interrupt access to your application – not good. So the pattern of drain – do the upgrade – uncordon – repeat should be what you’re doing to make sure that your applications are always available.