yum降级安装
yum downgrade kubelet-1.21.6 kubeadm-1.21.6 kubectl-1.21.6
更新kubelet kubeadm kubectl版本
yum update -y kubelet kubeadm kubectl
查看更新计划
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.19.0[upgrade/versions] kubeadm version: v1.20.1[upgrade/versions] Latest stable version: v1.20.1[upgrade/versions] Latest stable version: v1.20.1[upgrade/versions] Latest version in the v1.19 series: v1.19.6[upgrade/versions] Latest version in the v1.19 series: v1.19.6Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':COMPONENT CURRENT AVAILABLEkubelet 1 x v1.19.0 v1.19.61 x v1.19.2 v1.19.6Upgrade to the latest version in the v1.19 series:COMPONENT CURRENT AVAILABLEkube-apiserver v1.19.0 v1.19.6kube-controller-manager v1.19.0 v1.19.6kube-scheduler v1.19.0 v1.19.6kube-proxy v1.19.0 v1.19.6CoreDNS 1.6.7 1.7.0etcd 3.4.9-1 3.4.13-0You can now apply the upgrade by executing the following command:kubeadm upgrade apply v1.19.6_____________________________________________________________________Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':COMPONENT CURRENT AVAILABLEkubelet 1 x v1.19.0 v1.20.11 x v1.19.2 v1.20.1Upgrade to the latest stable version:COMPONENT CURRENT AVAILABLEkube-apiserver v1.19.0 v1.20.1kube-controller-manager v1.19.0 v1.20.1kube-scheduler v1.19.0 v1.20.1kube-proxy v1.19.0 v1.20.1CoreDNS 1.6.7 1.7.0etcd 3.4.9-1 3.4.13-0You can now apply the upgrade by executing the following command:kubeadm upgrade apply v1.20.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 orresetting to kubeadm defaults before a successful upgrade can be performed. The version to manuallyupgrade to is denoted in the "PREFERRED VERSION" column.API GROUP CURRENT VERSION PREFERRED VERSION MANUAL UPGRADE REQUIREDkubeproxy.config.k8s.io v1alpha1 v1alpha1 nokubelet.config.k8s.io v1beta1 v1beta1 no_____________________________________________________________________
更新kubernetes版本
kubeadm upgrade apply ${version} --v=5
修改etcd配置文件
apiVersion: v1kind: Podmetadata:annotations:kubeadm.kubernetes.io/etcd.advertise-client-urls: https://127.0.0.1:2379creationTimestamp: nulllabels:component: etcdtier: control-planename: etcdnamespace: kube-systemspec:containers:- command:- etcd- --advertise-client-urls=https://127.0.0.1:2379- --cert-file=/etc/kubernetes/pki/etcd/server.crt- --client-cert-auth=true- --data-dir=/var/lib/etcd- --initial-advertise-peer-urls=https://101.37.15.135:2380- --initial-cluster=izbp160f904j9af7s53jk7z=https://101.37.15.135:2380- --key-file=/etc/kubernetes/pki/etcd/server.key- --listen-client-urls=https://127.0.0.1:2379,https://127.0.0.1:2379- --listen-metrics-urls=http://127.0.0.1:2381- --listen-peer-urls=https://127.0.0.1:2380- --name=izbp160f904j9af7s53jk7z- --peer-cert-file=/etc/kubernetes/pki/etcd/peer.crt- --peer-client-cert-auth=true- --peer-key-file=/etc/kubernetes/pki/etcd/peer.key- --peer-trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt- --snapshot-count=10000- --trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crtimage: registry.aliyuncs.com/google_containers/etcd:3.4.13-0imagePullPolicy: IfNotPresent
kubeadm.kubernetes.io/etcd.advertise-client-urls,—advertise-client-urls,—listen-client-urls,—listen-peer-urls修改为127.0.0.1
重启kubelet
systemctl restart kubelet
