Why we don`t use version from kubeadm upgrade plan for upgrade kubernetes

Kubernetes
#1

Hello!
I try understand Udemy Labs - Certified Kubernetes Administrator with Practice Tests - KodeKloud step 9.

kubeadm upgrade plan

[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster…
[upgrade/config] FYI: You can look at this config file with ‘kubectl -n kube-system get cm kubeadm-config -oyaml’
[preflight] Running pre-flight checks.
[upgrade] Running cluster health checks
[upgrade] Fetching available versions to upgrade to
[upgrade/versions] Cluster version: v1.19.0
[upgrade/versions] kubeadm version: v1.19.0
I1123 12:52:25.951942 27140 version.go:252] remote version is much newer: v1.22.4; falling back to: stable-1.19
[upgrade/versions] Latest stable version: v1.19.16
[upgrade/versions] Latest stable version: v1.19.16
[upgrade/versions] Latest version in the v1.19 series: v1.19.16
[upgrade/versions] Latest version in the v1.19 series: v1.19.16

Components that must be upgraded manually after you have upgraded the control plane with ‘kubeadm upgrade apply’:
COMPONENT CURRENT AVAILABLE
kubelet 2 x v1.19.0 v1.19.16

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

COMPONENT CURRENT AVAILABLE
kube-apiserver v1.19.0 v1.19.16
kube-controller-manager v1.19.0 v1.19.16
kube-scheduler v1.19.0 v1.19.16
kube-proxy v1.19.0 v1.19.16
CoreDNS 1.7.0 1.7.0
etcd 3.4.9-1 3.4.9-1

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

    kubeadm upgrade apply v1.19.16

kubeadm offers to upgrade to v1.19.16
But we update to 1.20.0
Why we don`t use version from kubeadm upgrade plan for upgrade kubernetes ?
Thanks!

1
11920×1080 172 KB

#2

that’s because the current kubeadm is v1.19. try
apt update
apt install kubeadm=1.20.0-00
kubeadm upgrade plan

1 Like