Issue with Practice Test Cluster Upgrade Process

Kubernetes
#1

Error from validation:
Task not completed: Master Upgraded to v1.18.0

Output from upgrade plan:
[upgrade/versions] Cluster version: v1.18.0
[upgrade/versions] kubeadm version: v1.18.0
[upgrade/versions] Latest stable version: v1.18.6
[upgrade/versions] Latest stable version: v1.18.6
[upgrade/versions] Latest version in the v1.18 series: v1.18.6
[upgrade/versions] Latest version in the v1.18 series: v1.18.6

Components that must be upgraded manually after you have upgraded the control plane with ‘kubeadm upgrade apply’:
COMPONENT CURRENT AVAILABLE
Kubelet 1 x v1.17.0 v1.18.6
1 x v1.18.0 v1.18.6

Upgrade to the latest version in the v1.18 series:

COMPONENT CURRENT AVAILABLE
API Server v1.18.0 v1.18.6
Controller Manager v1.18.0 v1.18.6
Scheduler v1.18.0 v1.18.6
Kube Proxy v1.18.0 v1.18.6
CoreDNS 1.6.7 1.6.7
Etcd 3.4.3 3.4.3-0

Can you have a look, please ?

Update:
Same issue with worker node.
On master validation went through after I triggered another upgrade from 18.0 to 18.0 using hint command. This trick does not work on worker node thought.
Cluster upgrade validation works fine in lightning Lab, thought.

#2

Hello andrzej,
after upgrade apply, you should update kubelet manually. you can use: apt install kubelet=1.18.0-00

#3

I did this, but ok double check next time

#4

I am having some issues with this lab as well.

First issue, when you get access to the console you see the following error:

rm: cannot remove '/tmp/wait-script.sh': No such file or directory

I ran the lab twice just to make sure it was not an odd issue that was fixed with reloading it again.

Then on task 9 you are asked to upgrade to v1.18.0, but at that point the feedback from the console is telling you to upgrade to v1.17.9

[preflight] Running pre-flight checks.
[upgrade] Making sure the cluster is healthy:
[upgrade] Fetching available versions to upgrade to
[upgrade/versions] Cluster version: v1.17.0
[upgrade/versions] kubeadm version: v1.17.0
I0803 19:05:35.569081    4426 version.go:251] remote version is much newer: v1.18.6; falling back to: 
stable-1.17
[upgrade/versions] Latest stable version: v1.17.9
[upgrade/versions] Latest version in the v1.17 series: v1.17.9
Components that must be upgraded manually after you have upgraded the control plane with 
'kubeadm upgrade apply':
COMPONENT   CURRENT       AVAILABLE
Kubelet     2 x v1.17.0   v1.17.9
Upgrade to the latest version in the v1.17 series:
COMPONENT            CURRENT   AVAILABLE
API Server           v1.17.0   v1.17.9
Controller Manager   v1.17.0   v1.17.9
Scheduler            v1.17.0   v1.17.9
Kube Proxy           v1.17.0   v1.17.9
CoreDNS              1.6.5     1.6.5
Etcd                 3.4.3     3.4.3-0

You can now apply the upgrade by executing the following command:

    kubeadm upgrade apply v1.17.9

Note: Before you can perform this upgrade, you have to update kubeadm to v1.17.9.

This stumped me for a bit as it seemed to imply I couldn’t upgrade to 1.18 as requested in the question. I carried on with following what was asked in the question and managed to upgrade to v.1.18 but I feel the lab could do with a bit of work question wise as it is a bit misleading (from my point of view.)

#5

Hello, Rosarch
kubeadm version is 1.17 so kubeadm will display maximum high available version. When you upgrade kubeadm to version 1.18 then it will display 1.18 version series.

#6

Thanks player001, still think this lab needs an update as the aim is to carry out a simple upgrade for the first time, not to troubleshoot any issues, also the solution that follows it is out of synch. As in, the solution is meant to take you through all the questions and give tips on approaches to answer, it doesn’t as some of the questions are slightly different and you are installing 1.17 not 1.18. :man_shrugging: