Kubernetes V1.22.4升级到1.23.0

最新推荐文章于 2023-03-28 23:08:47 发布
最新推荐文章于 2023-03-28 23:08:47 发布
阅读量946 收藏 1
点赞数
文章标签： kubernetes 容器 docker
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u014796929/article/details/123256481
版权

一、首先更新下yum缓存

yum clean all
yum makecache

二、yum list 查一下最新的稳定版本

yum list --showduplicates kubeadm --disableexcludes=kubernetes

三、升级master

3.1、kubeadm 升级

yum install -y kubeadm-1.23.0 --disableexcludes=kubernetes

3.2、验证kubeadm 版本

kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:15:11Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}

3.3、排空master节点

kubectl drain k8s-master --ignore-daemonsets

3.4、验证升级计划

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.22.4
[upgrade/versions] kubeadm version: v1.23.0
[upgrade/versions] Target version: v1.23.3
[upgrade/versions] Latest version in the v1.22 series: v1.22.6

Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT   CURRENT       TARGET
kubelet     3 x v1.22.4   v1.22.6

Upgrade to the latest version in the v1.22 series:

COMPONENT                 CURRENT   TARGET
kube-apiserver            v1.22.4   v1.22.6
kube-controller-manager   v1.22.4   v1.22.6
kube-scheduler            v1.22.4   v1.22.6
kube-proxy                v1.22.4   v1.22.6
CoreDNS                   v1.8.4    v1.8.6
etcd                      3.5.0-0   3.5.1-0

You can now apply the upgrade by executing the following command:

        kubeadm upgrade apply v1.22.6

_____________________________________________________________________

Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
COMPONENT   CURRENT       TARGET
kubelet     3 x v1.22.4   v1.23.3

Upgrade to the latest stable version:

COMPONENT                 CURRENT   TARGET
kube-apiserver            v1.22.4   v1.23.3
kube-controller-manager   v1.22.4   v1.23.3
kube-scheduler            v1.22.4   v1.23.3
kube-proxy                v1.22.4   v1.23.3
CoreDNS                   v1.8.4    v1.8.6
etcd                      3.5.0-0   3.5.1-0

You can now apply the upgrade by executing the following command:

        kubeadm upgrade apply v1.23.3

Note: Before you can perform this upgrade, you have to update kubeadm to v1.23.3.

_____________________________________________________________________


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@k8s-master ~]#

3.5、选择要升级到的目标版本

如果不是第一个升级的master的话执行:kubeadm upgrade node

只有第一个升级的master执行:kubeadm upgrade apply操作

[root@k8s-master ~]#  kubeadm upgrade apply v1.23.0
[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.23.0"
[upgrade/versions] Cluster version: v1.22.4
[upgrade/versions] kubeadm version: v1.23.0
[upgrade/confirm] Are you sure you want to proceed with the upgrade? [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'
[upgrade/apply] Upgrading your Static Pod-hosted control plane to version "v1.23.0"...
Static pod: kube-apiserver-k8s-master hash: d3452b28e1fb9eb366cdbab36a7e88b2
Static pod: kube-controller-manager-k8s-master hash: 70395e6e769fd867813b902c45bece19
Static pod: kube-scheduler-k8s-master hash: ac2d970537ef80a81b00daf235de18e5
[upgrade/etcd] Upgrading to TLS for etcd
Static pod: etcd-k8s-master hash: e991ddf14a7b90b4e7430ec956ce1f5b
[upgrade/staticpods] Preparing for "etcd" upgrade
[upgrade/staticpods] Renewing etcd-server certificate
[upgrade/staticpods] Renewing etcd-peer certificate
[upgrade/staticpods] Renewing etcd-healthcheck-client certificate
[upgrade/staticpods] Moved new manifest to "/etc/kubernetes/manifests/etcd.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests-2022-02-10-15-09-44/etcd.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)
Static pod: etcd-k8s-master hash: e991ddf14a7b90b4e7430ec956ce1f5b
Static pod: etcd-k8s-master hash: c5549d895cdd0282f7ccc5201c46dd12
[apiclient] Found 1 Pods for label selector component=etcd
[upgrade/staticpods] Component "etcd" upgraded successfully!
[upgrade/etcd] Waiting for etcd to become available
[upgrade/staticpods] Writing new Static Pod manifests to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests698984810"
[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-2022-02-10-15-09-44/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)
Static pod: kube-apiserver-k8s-master hash: d3452b28e1fb9eb366cdbab36a7e88b2
Static pod: kube-apiserver-k8s-master hash: 6da47145944290f7c38fa6d826eda641
[apiclient] Found 1 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-2022-02-10-15-09-44/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)
Static pod: kube-controller-manager-k8s-master hash: 70395e6e769fd867813b902c45bece19
Static pod: kube-controller-manager-k8s-master hash: 8f65b494d0302a9ea95b3fec24f83b05
[apiclient] Found 1 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-2022-02-10-15-09-44/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)
Static pod: kube-scheduler-k8s-master hash: ac2d970537ef80a81b00daf235de18e5
Static pod: kube-scheduler-k8s-master hash: 28dad46d170cdc91ae0b7de16a4ff238
[apiclient] Found 1 Pods for label selector component=kube-scheduler
[upgrade/staticpods] Component "kube-scheduler" upgraded successfully!
[upgrade/postupgrade] Applying label node-role.kubernetes.io/control-plane='' to Nodes with label node-role.kubernetes.io/master='' (deprecated)
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.23" in namespace kube-system with the configuration for the kubelets in the cluster
NOTE: The "kubelet-config-1.23" naming of the kubelet ConfigMap is deprecated. Once the UnversionedKubeletConfigMap feature gate graduates to Beta the default name will become just "kubelet-config". Kubeadm upgrade will handle this transition transparently.
[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
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

[upgrade/successful] SUCCESS! Your cluster was upgraded to "v1.23.0". Enjoy!

[upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so.

3.5、取消对控制面节点的保护

[root@k8s-master ~]# kubectl uncordon k8s-master
node/k8s-master uncordoned

3.6、升级 kubelet 和 kubectl

[root@k8s-master ~]# yum install -y kubelet-1.23.0 kubectl-1.23.0 --disableexcludes=kubernetes
重启 kubelet
[root@k8s-master ~]# systemctl daemon-reload
[root@k8s-master ~]# systemctl restart kubelet

四、升级工作节点（node节点）

4.1、升级 kubeadm

[root@k8s-node01 ~]# yum install -y kubeadm-1.23.0 --disableexcludes=kubernetes

4.2、保护节点

[root@k8s-master ~]# kubectl drain k8s-node01  --ignore-daemonsets

4.3、升级 kubelet 配置

[root@k8s-node01 ~]# kubeadm upgrade node

4.4、升级 kubelet 与 kubectl

[root@k8s-node01 ~]# yum install -y kubelet-1.23.0 kubectl-1.23.0 --disableexcludes=kubernetes
重启 kubelet
[root@k8s-master ~]# systemctl daemon-reload
[root@k8s-master ~]# systemctl restart kubelet

4.5、取消对节点的保护

[root@k8s-master ~]# kubectl uncordon k8s-node01

五、验证集群

[root@k8s-master ~]# kubectl get nodes
NAME         STATUS                     ROLES                  AGE   VERSION
k8s-master   Ready                      control-plane,master   69d   v1.23.0
k8s-node01   Ready,SchedulingDisabled   <none>                 68d   v1.23.0
k8s-node02   Ready                      <none>                 68d   v1.23.0
大哥在北漂
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
k55.第十九章 K8s运维篇-集群升级 -- kubeadm v1.22 安装方式升级(一)
Raymond的博客
06-12 391
1.kubeadm 安装方式升级 升级k8s集群必须 先升级kubeadm版本到目的k8s版本，也就是说kubeadm是k8s升级的准升证。 1.1 升级准备 在k8s的所有master节点进行组件升级，将管理端服务kube-controller-manager、kube-apiserver、kube-scheduler、kube-proxy进行版本升级。 1.1.1 验证当前k8s master版本 [root@k8s-master01 ~]# kubeadm version kubeadm versio
K8S 生态周报| Kubernetes v1.23.0 正式发布，新特性一览
k8s 生态
12-08 916
“「K8S 生态周报」内容主要包含我所接触到的 K8S 生态相关的每周值得推荐的一些信息。欢迎订阅知乎专栏「k8s生态」[1]。”Kubernetes v1.23 今天正式发布，这是 20...
Kubernetes CKS v1.23 考试 实验 模拟环境 （最新考题搭建）
Vic的博客
03-19 1504
K8S CKS1.23 考试环境，按照CKS最新原题搭建的，模拟环境已集成考题，可直接模拟练习，做题实操。 资料包含：题库+答案+笔记+模拟环境+技术支持、排错答疑，2周即可练出并参加考试。包学包过，资料可长期更新，资料详见下方截图。 注意：考试中心在2022年2月21号，已升级CKS考试为1.23版本！3月15号题目略有变动。 操作系统版本：Ubuntu 20.04 Kubernetes版本：v1.23 与最新考试环境一致，最近部分同学考试为：2022年 2月25号（88分），2月24号（85分）.
kubernetes 版本从 1.26.6 升级到 1.27.9
为梦想奋斗
11-05 2539
kubernetes版本的升级主要是升级kubeadm、kubectl和kubelet，升级应遵循以下原则： 1、apiserver保护版本最大，其它功能最多比apiserver小一个小版本号。 2、不能跨小版本升级。 使用下列命令列出可用版本 yum list --showduplicates kubeadm --disableexcludes=kubernetes 我的环境包括一个...
kubeadm安装高可用K8S-1.19集群(外部etcd方式)
lswzw的博客
10-12 8047
kubeadm安装高可用K8S-1.19集群<外部etcd方式>集群规划初始化工作(master01-master02-node01都须要操作)安装步骤一、安装keepalived创建VIP二、搭建高可用etcd集群三、安装 kubeadm, kubelet 和 kubectl四、初始化master五、将worker节点加入集群六、安装插件flannel、metrics-server七、测试集群 外部二进制搭建etcd集群、系统出问题后还能通过外部etcd做恢复、操作上比直接把etcd放容器内好
Kubernetes v1.23.5 全离线资源安装包
03-31
Kubernetes v1.23.5 全离线资源安装包 用这些资料可以完整离线安装，有问题可以直接私信我给你解决。 镜像： kube-apiserver-v1.23.5.tar kube-controller-manager-v1.23.5.tar kube-proxy-v1.23.5.tar kube-...
kubernetes v1.23.3 源码包
02-17
下载链接 https://github.com/kubernetes/kubernetes/archive/refs/tags/v1.23.3.tar.gz
en.stm32cubef4_v1.23.0.zip
02-23
stm32cubeMX所需要的f4系列芯片的固件v1.23版本库
PL2303 Windows Driver Manual v1.23.0.pdf
最新发布
01-12
PL2303 Windows Driver Manual v1.23.0
PikPak安卓版 v1.23.0.apk
04-13
PikPak安卓版 v1.23.0.apk
CANalystv1.23
12-17
CAN分析仪软件，用于侦测CAN总线数据。
Kubernetes版本升级方法
听海归雪的博客
02-28 2162
主要是介绍kubernetes的版本升级方法，从v1.22.3升级到v1.22.17版本
K8S 升级
jiangbenchu的博客
05-27 901
v1.13.0 --> v1.14.2 K8S 升级可以跨小版本，但是不能跨大版本升级，只能一个大版本一个大版本的升级 v1.13.0 --> v1.14.2 正确 v1.13.0 --> v1.17.0 错误 1 升级 kubeadm (所有节点都执行kubeadm升级) # 查看当前集群版本 [root@test1 ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION test1 Ready mas
关于k8s 集群版本升级的一些笔记(不能跨次要版本升级)
山河已无恙
11-23 1697
生活的意义就是学着真实的活下去，生命的意义就是寻找生活的意义 -----山河已无恙
kubelet版本选择_通过 Kubeadm 升级 Kubernetes 版本
weixin_39697660的博客
12-20 569
!版权声明：本博客内容均均为原创,每篇博文作为知识积累,写博不易,转载请注明出处。目录[-]参考地址：系统环境：系统版本：CentOS 7.8内核版本：4.4.218-1升级前 kubernetes 版本：1.17.4升级后 kubernetes 版本：1.18.1注意事项：升级 Kubernetes 1.18+ 且使用 IPVS 模块，需要将 CentOS 内核版本升级至 4.4 +，否则 ku...
使用kubeadm 升级k8s
ice_bird的专栏
11-12 1422
检查当前kubeadm版本 [root@k8s-node2 ~]# rpm -qi kubeadm Name : kubeadm Version : 1.20.12 Release : 0 Architecture: x86_64 Install Date: Fri 12 Nov 2021 05:32:45 PM CST Group : Unspecified Size : 39219972 License : ASL 2.0 Signat
k8s创建资源(1)、「扩容与缩容」和「升级与回滚」
xgp666的博客
07-10 462
两种创建资源的方法 基于命令的方式： 简单直观快捷，上手快。 适合临时测试或实验。 基于配置文件的方式： 配置文件描述了 What，即应用最终要达到的状态。 配置文件提供了创建资源的模板，能够重复部署。 可以像管理代码一样管理部署。 适合正式的、跨环境的、规模化部署。 这种方式要求熟悉配置文件的语法，有一定难度。 一，用命令行的方式创建资源 主机 IP地址 master 192.168.1.21 node01 192.168.1.22 node02 192.168.1.23
升级Kubernetes集群的Docker版本
一切有为法，如梦亦如幻，如露亦如电，应作如是观。
10-02 1645
在Kubernetes集群中，组件版本升级非常快，可能需要不停的进行升级。升级master和node节点的Docker和Containerd，逐台升级，确保升级节点被驱逐时集群内有足够的资源承载负载，对于生产环境在升级前做好充足验证，避免版本变化而导致的异常产生。本次升级是在测试环境kubernetes集群版本是 v1.18.4，docker版本是19.03.8，这里，升级docker以及对应的Containerd到高版本，20.10.12。
带你深入学习k8s--(二)升级 kubeadm 集群
好久没说梦想的博客
03-28 483
本章介绍如何将kubeadm创建的 Kubernetes 集群从 1.23.x 版本升级到 1.24.x 版本以及从 1.24.x 升级到 1.25.x。请注意k8s官方不支持跨大版本升级。官方建议生产环境中每一年更新一次大版本。
pip install numpy==1.23.0 WARNING: The directory '/root/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag. Looking in indexes: https://mirrors.aliyun.com/pypi/simple/, https://pypi.tuna.tsinghua.edu.cn/simple/, https://pypi.douban.com/simple, https://pypi.mirrors.ustc.edu.cn/simple/ ERROR: Ignored the following versions that require a different python version: 1.22.0 Requires-Python >=3.8; 1.22.1 Requires-Python >=3.8; 1.22.2 Requires-Python >=3.8; 1.22.3 Requires-Python >=3.8; 1.22.4 Requires-Python >=3.8; 1.23.0 Requires-Python >=3.8; 1.23.0rc1 Requires-Python >=3.8; 1.23.0rc2 Requires-Python >=3.8; 1.23.0rc3 Requires-Python >=3.8; 1.23.1 Requires-Python >=3.8; 1.23.2 Requires-Python >=3.8; 1.23.3 Requires-Python >=3.8; 1.23.4 Requires-Python >=3.8; 1.23.5 Requires-Python >=3.8; 1.24.0 Requires-Python >=3.8; 1.24.0rc1 Requires-Python >=3.8; 1.24.0rc2 Requires-Python >=3.8; 1.24.1 Requires-Python >=3.8; 1.24.2 Requires-Python >=3.8; 1.24.3 Requires-Python >=3.8; 1.24.4 Requires-Python >=3.8; 1.25.0 Requires-Python >=3.9; 1.25.0rc1 Requires-Python >=3.9; 1.25.1 Requires-Python >=3.9 ERROR: Could not find a version that satisfies the requirement numpy==1.23.0 (from versions: 1.3.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1, 1.7.2, 1.8.0, 1.8.1, 1.8.2, 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.10.0.post2, 1.10.1, 1.10.2, 1.10.4, 1.11.0, 1.11.1, 1.11.2, 1.11.3, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 1.13.3, 1.14.0, 1.14.1, 1.14.2, 1.14.3, 1.14.4, 1.14.5, 1.14.6, 1.15.0, 1.15.1, 1.15.2, 1.15.3, 1.15.4, 1.16.0, 1.16.1, 1.16.2, 1.16.3, 1.16.4, 1.16.5, 1.16.6, 1.17.0, 1.17.1, 1.17.2, 1.17.3, 1.17.4, 1.17.5, 1.18.0, 1.18.1, 1.18.2, 1.18.3, 1.18.4, 1.18.5, 1.19.0, 1.19.1, 1.19.2, 1.19.3, 1.19.4, 1.19.5, 1.20.0, 1.20.1, 1.20.2, 1.20.3, 1.21.0, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6) ERROR: No matching distribution found for numpy==1.23.0 Note: you may need to restart the kernel to use updated packages.
07-13
这个错误消息显示找不到满足要求的numpy版本1.23.0。可能的原因是该版本的numpy要求使用Python 3.8及以上的版本，而你当前使用的Python版本可能较低。 你可以尝试以下几种解决方案： 1. 检查你当前使用的Python版本，确保它符合numpy 1.23.0的要求。如果需要更新Python版本，请参考相应的文档或使用适合你操作系统的包管理工具进行更新。 2. 如果你无法升级Python版本，你可以尝试安装一个较低版本的numpy，比如安装一个兼容Python版本的1.22.x系列的numpy。 3. 如果你需要使用特定的numpy版本，你可以尝试在其他地方寻找符合要求的二进制安装包，并手动安装。 另外，关于警告信息中提到的缓存目录权限问题，你需要确保当前用户对pip缓存目录（一般为`/root/.cache/pip`）或其父目录具有写权限。如果你是使用sudo运行pip命令，建议添加`-H`标志以确保使用正确的用户和环境。 最后，如果你在Jupyter Notebook中运行此命令，可能需要重启内核以使用更新后的包。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值