1.22-ről jöttem fel 1.31-re,
Azért ez merész, a tipikus upgrade path az a kettő közötti összes major (1.23, 1.24, ..., 1.30), úgy, hogy felhúzod az utolsó minor verzióra. És ezt is kifejezetten kubeadm paranccsal, például:
# 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 -o yaml'
[preflight] Running pre-flight checks.
[upgrade] Running cluster health checks
[upgrade] Fetching available versions to upgrade to
[upgrade/versions] Cluster version: v1.24.10
[upgrade/versions] kubeadm version: v1.24.10
I0930 07:35:25.927610 2937138 version.go:256] remote version is much newer: v1.31.1; falling back to: stable-1.24
[upgrade/versions] Target version: v1.24.17
[upgrade/versions] Latest version in the v1.24 series: v1.24.17
Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT CURRENT TARGET
kubelet 15 x v1.24.10 v1.24.17
Upgrade to the latest version in the v1.24 series:
COMPONENT CURRENT TARGET
kube-apiserver v1.24.10 v1.24.17
kube-controller-manager v1.24.10 v1.24.17
kube-scheduler v1.24.10 v1.24.17
kube-proxy v1.24.10 v1.24.17
CoreDNS v1.8.6 v1.8.6
etcd 3.5.6-0 3.5.6-0
You can now apply the upgrade by executing the following command:
kubeadm upgrade apply v1.24.17
Note: Before you can perform this upgrade, you have to update kubeadm to v1.24.17.Enélkül tipikusan szétesik a picsába, mint a mellékelt ábra is mutatja.
már ott tartok, h nulláról húzom újra, és 2 perc futás után minden ok nélkül lekapcsol a cluster
Ezzel kezdjed: `mv /etc/kubernetes/ /etc/kubernetes.old/; mv ~./kube/ ~./kube.old/`
Szerintem ott maradt egy csomó szemét, ami zavart okoz az erőben.