k8s 1.22单Master版本升级【开发/测试环境】

最新推荐文章于 2024-09-15 17:53:31 发布
最新推荐文章于 2024-09-15 17:53:31 发布
阅读量217 收藏
点赞数 1
分类专栏： k8s 文章标签： kubernetes 容器 云原生
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/demonlamei/article/details/136354400
版权
本文描述了如何使用kubeadm工具逐步升级Kubernetes集群的控制平面（master节点）和工作节点（worker节点），包括检查当前版本、选择升级目标、制定升级计划、手动配置升级以及验证升级后的状态。
摘要由CSDN通过智能技术生成

升级前状态查看

[root@node1 ~]# kubectl get node
NAME    STATUS   ROLES                  AGE     VERSION
node1   Ready    control-plane,master   3h15m   v1.22.17
node2   Ready    <none>                 3h13m   v1.22.17
node3   Ready    <none>                 3h13m   v1.22.17

master节点升级

[root@node1 ~]# yum  --showduplicates list kubeadm | grep 1.23
kubeadm.x86_64                       1.23.0-0                        kubernetes 
kubeadm.x86_64                       1.23.1-0                        kubernetes 
kubeadm.x86_64                       1.23.2-0                        kubernetes 
kubeadm.x86_64                       1.23.3-0                        kubernetes 
kubeadm.x86_64                       1.23.4-0                        kubernetes 
kubeadm.x86_64                       1.23.5-0                        kubernetes 
kubeadm.x86_64                       1.23.6-0                        kubernetes 
kubeadm.x86_64                       1.23.7-0                        kubernetes 
kubeadm.x86_64                       1.23.8-0                        kubernetes 
kubeadm.x86_64                       1.23.9-0                        kubernetes 
kubeadm.x86_64                       1.23.10-0                       kubernetes 
kubeadm.x86_64                       1.23.11-0                       kubernetes 
kubeadm.x86_64                       1.23.12-0                       kubernetes 
kubeadm.x86_64                       1.23.13-0                       kubernetes 
kubeadm.x86_64                       1.23.14-0                       kubernetes 
kubeadm.x86_64                       1.23.15-0                       kubernetes 
kubeadm.x86_64                       1.23.16-0                       kubernetes 
kubeadm.x86_64                       1.23.17-0                       kubernetes 

#升级到指定版本，大版本只能逐个按顺序升级，无法跳大版本
yum install kubeadm-1.23.17-0 -y

#查看升级计划
kubeadm upgrade plan
#输出信息如下
[root@node1 ~]# 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.17
[upgrade/versions] kubeadm version: v1.23.17
I0228 19:44:02.426057   22119 version.go:256] remote version is much newer: v1.29.2; falling back to: stable-1.23
[upgrade/versions] Target version: v1.23.17
[upgrade/versions] Latest version in the v1.22 series: v1.22.17

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.17   v1.23.17

Upgrade to the latest stable version:

COMPONENT                 CURRENT    TARGET
kube-apiserver            v1.22.17   v1.23.17
kube-controller-manager   v1.22.17   v1.23.17
kube-scheduler            v1.22.17   v1.23.17
kube-proxy                v1.22.17   v1.23.17
CoreDNS                   v1.8.4     v1.8.6
etcd                      3.5.6-0    3.5.6-0

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

        kubeadm upgrade apply v1.23.17

_____________________________________________________________________


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
_____________________________________________________________________

#执行升级计划
#！！！注意：升级过程集群可能无法正常进行变更操作，但是运行中的pod不受影响
kubeadm upgrade apply v1.23.17
#输出信息如下：
[root@node1 ~]# kubeadm upgrade apply v1.23.17
[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.17"
[upgrade/versions] Cluster version: v1.22.17
[upgrade/versions] kubeadm version: v1.23.17
[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.17"...
Static pod: kube-apiserver-node1 hash: f34895082fb5088a5fac6d790c649292
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
[upgrade/etcd] Upgrading to TLS for etcd
Static pod: etcd-node1 hash: 57baaca143aca45939625125cf9e7f4b
[upgrade/staticpods] Preparing for "etcd" upgrade
[upgrade/staticpods] Current and new manifests of etcd are equal, skipping upgrade
[upgrade/etcd] Waiting for etcd to become available
[upgrade/staticpods] Writing new Static Pod manifests to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests3684995289"
[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-02-28-19-45-32/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-node1 hash: f34895082fb5088a5fac6d790c649292
Static pod: kube-apiserver-node1 hash: f34895082fb5088a5fac6d790c649292
Static pod: kube-apiserver-node1 hash: f34895082fb5088a5fac6d790c649292
Static pod: kube-apiserver-node1 hash: 9e6226cb9df678a6ca35242eeb6a39ad
[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-2024-02-28-19-45-32/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-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: f71939c82c4c01af0bdc388ddb87ed55
Static pod: kube-controller-manager-node1 hash: 09e9af1b370c12b0af4fc4b118110202
[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-2024-02-28-19-45-32/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-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: db3d8203bf99f8af1ef287ca1ba16a39
Static pod: kube-scheduler-node1 hash: 88e4ded417ffd82a7c7d2c025e43d322
[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.17". Enjoy!

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

#更新kubelet\kubectl
yum  --showduplicates list kubelet | grep 1.23
yum  --showduplicates list kubectl | grep 1.23
yum install kubelet-1.23.17-0 kubectl-1.23.17-0 -y

#重启kubelet服务
systemctl daemon-reload
systemctl restart kubelet

#master节点升级完成，查看状态
[root@node1 ~]# kubectl get node
NAME    STATUS   ROLES                  AGE     VERSION
node1   Ready    control-plane,master   3h26m   v1.23.17
node2   Ready    <none>                 3h24m   v1.22.17
node3   Ready    <none>                 3h24m   v1.22.17

worker节点升级

#升级组件
yum install kubelet-1.23.17-0 kubectl-1.23.17-0 -y

#重启服务
systemctl daemon-reload
systemctl restart kubelet

#升级完成，查看状态
[root@node1 ~]# kubectl get node
NAME    STATUS   ROLES                  AGE     VERSION
node1   Ready    control-plane,master   3h28m   v1.23.17
node2   Ready    <none>                 3h26m   v1.23.17
node3   Ready    <none>                 3h26m   v1.23.17
demonlamei
关注
专栏目录
k8s,1.21升级为1.22后升级内置服务的脚本
02-14
k8s从1.21升级为1.22（k8s和节点分组都要升级） 官网地址：https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml ingreass 部分语法有变更，不支持 serviceName，service...
K8S 之master 节点的安装与配置
工作中的点点滴滴
05-13 8046
之前我们已经把K8s的必要组件etcd flanneld 和相关的证书都已经安装好了，现在我们来安装k8s的主节点。 下载地址 https://github.com/kubernetes/kubernetes/releases 在列表中选择对应的版本。如： wget https://dl.k8s.io/v1.10.2/kubernetes-server-linux-amd64.tar.gz...
【k8s】单master到多master平滑升级
weixin_45066823的博客
08-30 1964
由于单master节点用于线上环境发生故障时会导致集群整个不可用，生产环境中有很大风险所以要把集群升级为多master模式，其中任何一个节点宕机都不影响集群正常运行。将 kube-system 中的 kubeadm-config 配置导出，并修改配置。因为被删除的节点不是很“干净”，所以还需要把/etc/kubernets下的内容移除。根据上面操作的信息屏凑一个加入主节点的命令，在新加入的2个主节点执行。修改kubeadm-config中api-server地址。发现新的证书已经更新的。.........
kubernetes集群-Master节点升级-kubeadm,kubectl,kubelet升级
北海牧野
07-03 2220
kubernetes - Master单节点升级 kubeadm 升级 kubelet 升级 kubectl 升级 生产环境注意事项： 由于 kubeadm upgrade 不会升级 etcd，请确保已对其进行了备份。例如，您可以使用 etcdctl backup 命令完成这个工作。 请注意，kubeadm upgrade 只会升级 Kubernetes 内建（Kubernetes-internal）组件，不会触及任何工作负载。作为最佳实践，您应该备份所有重要数据。例如任何应用层级的状态数据，如应用可能依
【Kubernetes】k8s集群升级详细说明【k8s升级 kubeadm 集群】【万能版本升级方法】
崔崇鑫的博客，你linux/云运维工作中的百科全书。
12-02 6961
文章目录说明【必看】环境现有版本查看和升级版本说明升级流程【master节点】说明【必看】1、把节点执行drain操作报错error: unable to drain node ..处理正常dran显示2、升级kubeadm在线升级离线升级3、升级各个组建【apiserver、etcd，dns等】查看升级计划升级各个组建【不含etcd】4、取消drain操作5、升级kubelet和kubectl6、重启kubelet服务并验证多master升级说明升级流程【worker/node节点】说明【必看】1、把no
k8s v1.22.13版本离线安装包
10-13
只支持centos7.6操作系统，其他系统未经过测试，解压tar包，执行install_kubernetes.sh脚本即可自动安装
K8S离线资源包kube1.22.8.tar.gz
10-22
快速部署K8S,sealos 一键安装： “sealos init --passwd 123456 --master 10.10.1.60 --node 10.10.1.61 --pkg-url kube1.22.8.tar.gz --version v1.22.8”
超级kubeadm 高可用k8s-master用
08-14
目前kubernetes高可用需要要么依赖外部负载均衡器，自己搭建时就需要做keepalived haproxy等，比较麻烦，在某些云上可能keepalived还无法...sealyun定制超级版kubeadm通过ipvs代理多个master，优雅解决k8s高可用问题。
Kubeadm安装K8S单master节点集群
05-24
### Kubeadm安装K8S单Master节点集群详解 #### 一、集群环境规划与配置 根据提供的文档信息，我们了解到本次安装的目标是构建一个基于Kubeadm的Kubernetes (K8S) 单Master节点集群。该集群的具体规划如下： - **...
k8s 容忍和污点
batman
09-12 673
该值定义尽量避免将Pod调度到存在其不能容忍的Taint的节点上，但并不是强制的，也就是说，一个没有配置Toleration的Pod会优先部署至其他节点，没有其他可以调度的节点时，还是可以部署到effect为PreferNoSchedule的节点上的，NoSchedule没有这种机制。如果未被过滤的Taint中不存在effect值为NoExecute的Taint，但是存在effect值为PreferNoSchedule的Taint，则Kubernetes会尝试将Pod分配到该节点。
9.11-kubeadm方式安装k8s
qq_70752758的博客
09-11 594
配置pod的yaml文件和docker-compose.uaml文件相似。
k8s防火墙networkPolicy，的核心是“自己”
2401_84019227的博客
09-11 890
xxx.xxx.xx.x/32 # 允许某个网段，但除了这个ip。2. 从哪个名称空间进来的，就设置namespaceSelector，k8s的防火墙，考虑如何配置，就是从“自己”出发，去看待流量的流向。4. 从哪些标签的pod来的，就设置podSelector。是允许哪些流量来访问我，就是ingress from，1. 从哪个端口进来的，就设置ports，3. 从哪些ip来的，就设置ipBlock。那么，没有说明的，就是不让ingress。写了规则的，是允许进入和出去的流量。
k8s防火墙networkPolicy，其他规则和端口规则ports的匹配顺序，进站策略ingress和出站策略egress中，ports规则的常用方法。
2401_84019227的博客
09-11 533
有了这个先后顺序，相对就容易理解其他规则和ports规则的匹配关系。看ip报文里面封装的TCP/UDP报文中的端口号。因为端口信息是在打开ip包之后才能看到的。如果不接收，就不会有检测端口号的操作，端口策略和其他策略的顺序关系是什么。ports这个策略，和前面三个不同。ingress.from进站策略中。如果要求，只能访问什么端口，就是与。而是说，能访问所有主机的什么端口。egress.to出站策略中。如果没有强调只能访问什么端口。B接收到数据包是先看ip。各个规则和端口号的关系。各个规则和端口号的关系。
【从问题中去学习k8s】k8s中的常见面试题（夯实理论基础）（二十九）
zerotoall的博客
09-11 388
思考一下问题： 97、您认为公司如何处理服务器及其安装？ 考虑一家拼车公司希望通过同时扩展其平台来增加服务器数量。 您认为公司如何处理服务器及其安装？ 参考答案：
k8s环境搭建
qq_69920145的博客
09-11 845
imageRepository: registry.cn-hangzhou.aliyuncs.com/google_containers # 指定了Kubernetes使用的镜像仓库的地址，阿里云的镜像仓库。使用model主机克隆三台新的主机，名称分别为k8s_master，k8s_node01，k8s_node02，运行环境脚本，设置ip地址和名称，IP地址分别为66、77、88，并设置免密登录。net.ipv4.conf.all.route_localnet = 1 # 允许本地网络上的路由。
93、k8s之hpa+helm
m0_74149099的博客
09-12 945
pod的数量进行扩缩容针对对控制器创建的podreplicas:静态：editHPA：基于cpu的利用率来实现pod的数量大的自动伸缩。yaml 文件------主流------>必须要有资源控制的字段才能生效。命令行 生成HPA的配置。yaml必要条件：前置必要条件：控制器创建，而且必须能设置副本数配置的必要条件：必须要声明pod的资源控制1、metrices-server hpa使用的依赖环境。k8s使用集群资源的集中查询器。收集资源使用数据，给hpa，scheduller使用。
flink on k8s
最新发布
JavaCoder_juejue的博客
09-15 1075
echo "示例: $0 'k8s01 k8s02 k8s03 k8s04 k8s05' /path/to/file /remote/directory"echo "示例: $0 'k8s01 k8s02 k8s03 k8s04 k8s05' 'cd /aaa/bbb;echo "正在将文件 $SOURCE_FILE 传输到 $SERVER:$REMOTE_DIR..."echo "用法: $0 '服务器列表' '要传输的文件路径' '远程目标目录'"echo "用法: $0 '主机列表' '命令列表'"
92、K8s之ingress下集
m0_74149099的博客
09-11 1409
ingress----根据servicename选择service-----service把服务把请求根据匹配的标签转发pod。支持http 80 https 443。
kubeadm方式安装k8s续：
m0_70848838的博客
09-12 1698
等一会，如果还是没连上，查看节点错误日志vim /var/log/message，shift+g跳转到最后一行（如果都没有pending就是网络问题）错误1：Centos 7 系列操作系统在安装k8s时可能会遇到hostPath type check failed：/sys/fs/bpf is not a direcctory错误，该问题为内核版本过低导致的。/sys/fs/bpf 在4.4版本中的内核中才有，对于版本比较高得k8s集群建议升级内核到4.4以上。
k8s1.22版本升级
02-05
k8s 1.22版本升级是指将Kubernetes集群的版本从当前版本升级到1.22版本。Kubernetes是一个开源的容器编排平台，用于管理和部署容器化应用程序。每个Kubernetes版本都会带来一些新功能、改进和错误修复，升级到新版本...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值