您好,登錄后才能下訂單哦!
本篇內容介紹了“Kubernetes 1.17.2怎么快速升級”的有關知識,在實際案例的操作過程中,不少人都會遇到這樣的困境,接下來就讓小編帶領大家學習一下如何處理這些情況吧!希望大家仔細閱讀,能夠學有所成!
sudo apt install kubeadm=1.17.2-00 kubectl=1.17.2-00 kubelet=1.17.2-00
設置中國區的軟件源,參考: kubernetes for china
查看該版本的容器鏡像版本:
kubeadm config images list
輸出如下:
~# kubeadm config images listk8s.gcr.io/kube-apiserver:v1.17.2k8s.gcr.io/kube-controller-manager:v1.17.2k8s.gcr.io/kube-scheduler:v1.17.2k8s.gcr.io/kube-proxy:v1.17.2k8s.gcr.io/pause:3.1k8s.gcr.io/etcd:3.4.3-0k8s.gcr.io/coredns:1.6.5
原始的kubernetes鏡像文件在gcr上,不能直接下載。我給鏡像到了阿里云的杭州機房的容器倉庫里,拉取還是比較快的。
echo ""echo "=========================================================="echo "Pull Kubernetes v1.17.2 Images from aliyuncs.com ......"echo "=========================================================="echo ""MY_REGISTRY=registry.cn-hangzhou.aliyuncs.com/openthings## 拉取鏡像docker pull ${MY_REGISTRY}/k8s-gcr-io-kube-apiserver:v1.17.2 docker pull ${MY_REGISTRY}/k8s-gcr-io-kube-controller-manager:v1.17.2 docker pull ${MY_REGISTRY}/k8s-gcr-io-kube-scheduler:v1.17.2 docker pull ${MY_REGISTRY}/k8s-gcr-io-kube-proxy:v1.17.2 docker pull ${MY_REGISTRY}/k8s-gcr-io-etcd:3.4.3-0 docker pull ${MY_REGISTRY}/k8s-gcr-io-pause:3.1 docker pull ${MY_REGISTRY}/k8s-gcr-io-coredns:1.6.5## 添加Tagdocker tag ${MY_REGISTRY}/k8s-gcr-io-kube-apiserver:v1.17.2 k8s.gcr.io/kube-apiserver:v1.17.2 docker tag ${MY_REGISTRY}/k8s-gcr-io-kube-scheduler:v1.17.2 k8s.gcr.io/kube-scheduler:v1.17.2 docker tag ${MY_REGISTRY}/k8s-gcr-io-kube-controller-manager:v1.17.2 k8s.gcr.io/kube-controller-manager:v1.17.2 docker tag ${MY_REGISTRY}/k8s-gcr-io-kube-proxy:v1.17.2 k8s.gcr.io/kube-proxy:v1.17.2 docker tag ${MY_REGISTRY}/k8s-gcr-io-etcd:3.4.3-0 k8s.gcr.io/etcd:3.4.3-0 docker tag ${MY_REGISTRY}/k8s-gcr-io-pause:3.1 k8s.gcr.io/pause:3.1 docker tag ${MY_REGISTRY}/k8s-gcr-io-coredns:1.6.5 k8s.gcr.io/coredns:1.6.5echo ""echo "=========================================================="echo "Pull Kubernetes v1.17.2 Images FINISHED."echo "into registry.cn-hangzhou.aliyuncs.com/openthings, "echo " by openthings@https://my.oschina.net/u/2306127."echo "=========================================================="echo ""
保存為shell腳本,然后執行。
或者,下載腳本:https://github.com/openthings/kubernetes-tools/blob/master/kubeadm/2-images/
全新安裝:
#指定IP地址,1.17.2版本:sudo kubeadm init --kubernetes-version=v1.17.2 --apiserver-advertise-address=10.1.1.199 --pod-network-cidr=10.244.0.0/16
使用kubeadm部署高可用Kubernetes 1.17.0
先查看一下需要升級的各個組件的版本。
使用kubeadm upgrade plan ,輸出的版本升級信息如下:
Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply': COMPONENT CURRENT AVAILABLE Kubelet 1 x v1.17.0 v1.17.2 8 x v1.17.1 v1.17.2 Upgrade to the latest version in the v1.17 series: COMPONENT CURRENT AVAILABLE API Server v1.17.1 v1.17.2 Controller Manager v1.17.1 v1.17.2 Scheduler v1.17.1 v1.17.2 Kube Proxy v1.17.1 v1.17.2 CoreDNS 1.6.5 1.6.5 Etcd 3.4.3 3.4.3-0 You can now apply the upgrade by executing the following command: kubeadm upgrade apply v1.17.2
確保上面的容器鏡像已經下載(如果沒有提前下載,可能被網絡阻隔導致掛起),然后執行升級:
kubeadm upgrade -y apply v1.17.2
看到下面信息,就OK了。
[upgrade/successful] SUCCESS! Your cluster was upgraded to "v1.17.2". Enjoy!
然后,配置當前用戶環境:
mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
就可以使用 kubectl version 來查看狀態和 kubectl cluster-info 查看服務地址。
每個工作節點需要拉取上面對應版本的鏡像,以及安裝kubelet的對應版本。
檢查版本:
~$ kubectl version
查看Pod信息:
kubectl get pod --all-namespaces
“Kubernetes 1.17.2怎么快速升級”的內容就介紹到這里了,感謝大家的閱讀。如果想了解更多行業相關的知識可以關注億速云網站,小編將為大家輸出更多高質量的實用文章!
免責聲明:本站發布的內容(圖片、視頻和文字)以原創、轉載和分享為主,文章觀點不代表本網站立場,如果涉及侵權請聯系站長郵箱:is@yisu.com進行舉報,并提供相關證據,一經查實,將立刻刪除涉嫌侵權內容。