- Начинаем в маcтер ноды
- Узнаем таргет версию на гитхабе и обновляем kubeadm на controlnode
apt-mark unhold kubeadm && \
apt-get update && apt-get install -y kubeadm=1.26.1-00 && \
apt-mark hold kubeadm
Получаем сводную информацию до какой версии сможем обновиться.
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.25.0
[upgrade/versions] kubeadm version: v1.26.1
[upgrade/versions] Target version: v1.26.1
[upgrade/versions] Latest version in the v1.25 series: v1.25.6
W0120 20:38:43.075526 21295 configset.go:177] error unmarshaling configuration schema.GroupVersionKind{Group:"kubeproxy.config.k8s.io", Version:"v1alpha1", Kind:"KubeProxyConfiguration"}: strict decoding error: unknown field "udpIdleTimeout"
Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT CURRENT TARGET
kubelet 2 x v1.25.0 v1.25.6
Upgrade to the latest version in the v1.25 series:
COMPONENT CURRENT TARGET
kube-apiserver v1.25.0 v1.25.6
kube-controller-manager v1.25.0 v1.25.6
kube-scheduler v1.25.0 v1.25.6
kube-proxy v1.25.0 v1.25.6
CoreDNS v1.9.3 v1.9.3
etcd 3.5.4-0 3.5.6-0
You can now apply the upgrade by executing the following command:
kubeadm upgrade apply v1.25.6
_____________________________________________________________________
Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT CURRENT TARGET
kubelet 2 x v1.25.0 v1.26.1
Upgrade to the latest stable version:
COMPONENT CURRENT TARGET
kube-apiserver v1.25.0 v1.26.1
kube-controller-manager v1.25.0 v1.26.1
kube-scheduler v1.25.0 v1.26.1
kube-proxy v1.25.0 v1.26.1
CoreDNS v1.9.3 v1.9.3
etcd 3.5.4-0 3.5.6-0
You can now apply the upgrade by executing the following command:
kubeadm upgrade apply v1.26.1
_____________________________________________________________________
The table below shows the current state of component configs as understood by this version of kubeadm.
Configs that have a "yes" mark in the "MANUAL UPGRADE REQUIRED" column require manual config upgrade or
resetting to kubeadm defaults before a successful upgrade can be performed. The version to manually
upgrade to is denoted in the "PREFERRED VERSION" column.
API GROUP CURRENT VERSION PREFERRED VERSION MANUAL UPGRADE REQUIRED
kubeproxy.config.k8s.io v1alpha1 v1alpha1 no
kubelet.config.k8s.io v1beta1 v1beta1 no
_____________________________________________________________________
Драйним ноду(Заставляем все приложения перейти на другую ноду)(этого делать не нужно если там не было приложений)
k drain controlplane --ignore-daemonsets
Запускаем обновление кластера
sudo kubeadm upgrade apply v1.26.x
Далее обновляем kublet and kubectl and restart
apt-mark unhold kubelet kubectl && \
apt-get update && apt-get install -y kubelet=1.26.х-00 kubectl=1.26.х-00 && \
apt-mark hold kubelet kubectl
sudo systemctl daemon-reload
sudo systemctl restart kubelet
Разкордование нашу мастер ноду (этого делать не нужно если там не было приложений)
k uncordon controlplane
Обновляем ноду
apt-mark unhold kubelet kubectl && \
apt-get update && apt-get install -y kubelet=1.26.0-00 kubectl=1.26.0-00 && \
apt-mark hold kubelet kubectl
sudo systemctl daemon-reload
sudo systemctl restart kubelet
k uncordon node01