环境：https://www.cnblogs.com/yangmeichong/p/17956335
# 流程：先升级master，再升级node # 1.备份组件(etcd这里先不备份了) # 先升级master3 # 1.腾空节点，驱逐master # 1.1 节点设置为维护状态 [root@master ~]# kubectl cordon master3 node/master3 cordoned [root@master ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION master Ready control-plane 5h2m v1.28.2 master2 Ready control-plane 4h50m v1.28.2 master3 Ready,SchedulingDisabled control-plane 4h49m v1.28.2 node1 Ready worker 3h14m v1.28.2 # 1.2 驱逐节点上的pod [root@master ~]# kubectl drain master3 --delete-emptydir-data --ignore-daemonsets --force node/master3 already cordoned Warning: ignoring DaemonSet-managed Pods: kube-system/calico-node-c56kn, kube-system/kube-proxy-phdlz evicting pod kube-system/coredns-6554b8b87f-cjtsk evicting pod kube-system/calico-kube-controllers-7ddc4f45bc-76zdb evicting pod kube-system/coredns-6554b8b87f-ccvtm pod/calico-kube-controllers-7ddc4f45bc-76zdb evicted pod/coredns-6554b8b87f-cjtsk evicted pod/coredns-6554b8b87f-ccvtm evicted node/master3 drained # 1.3 查看可升级的版本 参考：https://v1-28.docs.kubernetes.io/zh-cn/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/ [root@master3 yum.repos.d]# yum list --showduplicates kubeadm --disableexcludes=kubernetes # 1.4 升级kubeadm yum install -y kubeadm-'1.28.x-*' --disableexcludes=kubernetes # 1.5 验证升级计划 [root@master3 yum.repos.d]# kubeadm version kubeadm version: &version.Info{Major:"1", Minor:"28", GitVersion:"v1.28.5", GitCommit:"506050d61cf291218dfbd41ac93913945c9aa0da", GitTreeState:"clean", BuildDate:"2023-12-19T13:40:52Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"} [root@master3 yum.repos.d]# kubeadm upgrade plan # 1.5 选择升级版本v1.28.5 ,忽略etcd升级 [root@master3 ~]# kubeadm upgrade apply v1.28.5 --etcd-upgrade=false 成功显示： [upgrade/successful] SUCCESS! Your cluster was upgraded to "v1.28.5". Enjoy! # 1.6 升级其他组件kubelet,kubectl [root@master3 ~]# yum install -y kubelet-1.28.5 kubectl-1.28.5 --disableexcludes=kubernetes [root@master3 ~]# kubelet --version Kubernetes v1.28.5 [root@master3 ~]# kubectl version Client Version: v1.28.5 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.28.5 #1.7 重启服务 systemctl daemon-reload systemctl restart kubelet # 1.8 将节点设置为可调度状态 [root@master3 ~]# kubectl uncordon master3 node/master3 uncordoned [root@master3 ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION master Ready control-plane 5h25m v1.28.2 master2 Ready control-plane 5h13m v1.28.2 master3 Ready control-plane 5h12m v1.28.5 node1 Ready worker 3h37m v1.28.2
[root@master3 yum.repos.d]# 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.28.2 [upgrade/versions] kubeadm version: v1.28.5 I0110 18:31:04.904312 103974 version.go:256] remote version is much newer: v1.29.0; falling back to: stable-1.28 [upgrade/versions] Target version: v1.28.5 [upgrade/versions] Latest version in the v1.28 series: v1.28.5 Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply': COMPONENT CURRENT TARGET kubelet 4 x v1.28.2 v1.28.5 Upgrade to the latest version in the v1.28 series: COMPONENT CURRENT TARGET kube-apiserver v1.28.2 v1.28.5 kube-controller-manager v1.28.2 v1.28.5 kube-scheduler v1.28.2 v1.28.5 kube-proxy v1.28.2 v1.28.5 CoreDNS v1.10.1 v1.10.1 etcd 3.5.9-0 3.5.9-0 You can now apply the upgrade by executing the following command: kubeadm upgrade apply v1.28.5 _____________________________________________________________________ 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 _____________________________________________________________________
[root@master3 ~]# kubeadm upgrade apply v1.28.5 --etcd-upgrade=false [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/version] You have chosen to change the cluster version to "v1.28.5" [upgrade/versions] Cluster version: v1.28.2 [upgrade/versions] kubeadm version: v1.28.5 [upgrade] Are you sure you want to proceed? [y/N]: y [upgrade/prepull] Pulling images required for setting up a Kubernetes cluster [upgrade/prepull] This might take a minute or two, depending on the speed of your internet connection [upgrade/prepull] You can also perform this action in beforehand using 'kubeadm config images pull' W0110 18:36:50.707322 106437 checks.go:835] detected that the sandbox image "registry.aliyuncs.com/google_containers/pause:3.7" of the container runtime is inconsistent with that used by kubeadm. It is recommended that using "registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.9" as the CRI sandbox image. [upgrade/apply] Upgrading your Static Pod-hosted control plane to version "v1.28.5" (timeout: 5m0s)... [upgrade/staticpods] Writing new Static Pod manifests to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests1651974058" [upgrade/staticpods] Preparing for "kube-apiserver" upgrade [upgrade/staticpods] Renewing apiserver certificate [upgrade/staticpods] Renewing apiserver-kubelet-client certificate [upgrade/staticpods] Renewing front-proxy-client certificate [upgrade/staticpods] Renewing apiserver-etcd-client certificate [upgrade/staticpods] Moved new manifest to "/etc/kubernetes/manifests/kube-apiserver.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests-2024-01-10-18-36-50/kube-apiserver.yaml" [upgrade/staticpods] Waiting for the kubelet to restart the component [upgrade/staticpods] This might take a minute or longer depending on the component/version gap (timeout 5m0s) [apiclient] Found 3 Pods for label selector component=kube-apiserver [upgrade/staticpods] Component "kube-apiserver" upgraded successfully! [upgrade/staticpods] Preparing for "kube-controller-manager" upgrade [upgrade/staticpods] Renewing controller-manager.conf certificate [upgrade/staticpods] Moved new manifest to "/etc/kubernetes/manifests/kube-controller-manager.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests-2024-01-10-18-36-50/kube-controller-manager.yaml" [upgrade/staticpods] Waiting for the kubelet to restart the component [upgrade/staticpods] This might take a minute or longer depending on the component/version gap (timeout 5m0s) [apiclient] Found 3 Pods for label selector component=kube-controller-manager [upgrade/staticpods] Component "kube-controller-manager" upgraded successfully! [upgrade/staticpods] Preparing for "kube-scheduler" upgrade [upgrade/staticpods] Renewing scheduler.conf certificate [upgrade/staticpods] Moved new manifest to "/etc/kubernetes/manifests/kube-scheduler.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests-2024-01-10-18-36-50/kube-scheduler.yaml" [upgrade/staticpods] Waiting for the kubelet to restart the component [upgrade/staticpods] This might take a minute or longer depending on the component/version gap (timeout 5m0s) [apiclient] Found 3 Pods for label selector component=kube-scheduler [upgrade/staticpods] Component "kube-scheduler" upgraded successfully! [upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace [kubelet] Creating a ConfigMap "kubelet-config" in namespace kube-system with the configuration for the kubelets in the cluster [upgrade] Backing up kubelet config file to /etc/kubernetes/tmp/kubeadm-kubelet-config690952238/config.yaml [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster [upgrade/addons] skip upgrade addons because control plane instances [master master2] have not been upgraded [upgrade/successful] SUCCESS! Your cluster was upgraded to "v1.28.5". Enjoy! [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so.