k8s集群修改节点和master的hostname之后需要如何调整（踩坑之旅）

最新推荐文章于 2024-08-24 19:36:00 发布
最新推荐文章于 2024-08-24 19:36:00 发布
阅读量4.7k 收藏 14
点赞数 3
分类专栏： 运维 文章标签： kubernetes
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/chenshm/article/details/118718644
版权

我把k8s集群master和node的hostname全部修改后发现kube ndoes 还是原来的样子

[root@k8s-master1 ~]# kubectl get nodes
NAME            STATUS   ROLES    AGE   VERSION
k8s-master-m1   Ready    master   13h   v1.15.1
k8s-node-n1     Ready    <none>   13h   v1.15.1
k8s-node-n2     Ready    <none>   13h   v1.15.1

当前的hostname已经经过下面的修改
k8s-master-m1->k8s-master1
k8s-node-n1->k8s-node1
k8s-node-n2->k8s-node2

怎么修改kube nodes的hostname呢？
1 台 master 加入集群后发现忘了修改主机名，而在 k8s 集群中修改节点主机名非常麻烦，不如将 master 退出集群改名并重新加入集群
接下来我试着先把nodes删除

[root@k8s-master1 ~]# kubectl delete node k8s-node-n1
node "k8s-node-n1" deleted
[root@k8s-master1 ~]# kubectl delete node k8s-node-n2
node "k8s-node-n2" deleted
[root@k8s-master1 ~]# kubectl delete node k8s-master-m1
node "k8s-master-m1" deleted
[root@k8s-master1 ~]# kubectl get nodes
No resources found.

全部删除了
查看csr

[root@k8s-master1 ~]# kubectl get csr
The connection to the server 192.168.32.29:6443 was refused - did you specify the right host or port?

开始提示host不正确了
执行kubeadm reset命令清除集群所有的配置

[root@k8s-master1 ~]# kubeadm reset
[reset] Reading configuration from the cluster...
[reset] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
[preflight] Running pre-flight checks
[reset] Removing info for node "k8s-master1" from the ConfigMap "kubeadm-config" in the "kube-system" Namespace
W0524 13:31:14.677131  127888 removeetcdmember.go:61] [reset] failed to remove etcd member: error syncing endpoints with etc: etcdclient: no available endpoints
.Please manually remove this etcd member using etcdctl
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/etcd /var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually.
For example:
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

提示不能清除kubeconfig files, 需要我手动去删除
直接手动删除

rm -rf $HOME/.kube/config

再重新reset,还是会遇到以下提示

[root@k8s-master1 ~]# kubeadm reset
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
[preflight] Running pre-flight checks
W0524 13:41:55.276661  128746 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually.
For example:
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

reset iptables, 再reset kubeconfig， 还是没有解决问题

[root@k8s-master1 ~]# iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X
[root@k8s-master1 ~]# kubeadm reset
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
[preflight] Running pre-flight checks
W0524 13:45:44.825195  128954 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually.
For example:
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

尝试按照提示先clear system’s IPVS tables，再reset集群配置,还是失败了

[root@k8s-master1 ~]# ipvsadm --clear
[root@k8s-master1 ~]# kubeadm reset
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
[preflight] Running pre-flight checks
W0524 13:50:29.415380  129229 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually.
For example:
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

只好放大招了！！！
修改kubeadm-config.yaml里面的nodeRegistration的name为master的新hostname先

nodeRegistration:
  criSocket: /var/run/dockershim.sock
  name: k8s-master1
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master

然后执行如下命令，重新初始化主节点和部署

kubeadm init --config=kubeadm-config.yaml --experimental-upload-certs | tee kubeadm-init.log

然后再执行以下命令，发现master节点出来了，并且用上了新的hostname

[root@k8s-master1 ~]# mkdir -p $HOME/.kube
[root@k8s-master1 ~]# cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@k8s-master1 ~]# chown $(id -u):$(id -g) $HOME/.kube/config
[root@k8s-master1 ~]# kubectl get nodes
NAME          STATUS     ROLES    AGE   VERSION
k8s-master1   NotReady   master   53s   v1.15.1

重新部署kube flannel网络插件 — 只需要在主节点执行, master节点就ready了

[root@k8s-master1 ~]# kubectl create -f kube-flannel.yml
podsecuritypolicy.policy/psp.flannel.unprivileged created
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
daemonset.apps/kube-flannel-ds-amd64 created
daemonset.apps/kube-flannel-ds-arm64 created
daemonset.apps/kube-flannel-ds-arm created
daemonset.apps/kube-flannel-ds-ppc64le created
daemonset.apps/kube-flannel-ds-s390x created
[root@k8s-master1 ~]# kubectl get nodes
NAME          STATUS   ROLES    AGE     VERSION
k8s-master1   Ready    master   8m15s   v1.15.1

部署完毕再查询pod，发现一切运行良好

[root@k8s-master1 ~]# kubectl get pod -n kube-system
NAME                                  READY   STATUS    RESTARTS   AGE
coredns-5c98db65d4-jbhww              1/1     Running   0          11m
coredns-5c98db65d4-jdqtn              1/1     Running   0          11m
etcd-k8s-master1                      1/1     Running   0          10m
kube-apiserver-k8s-master1            1/1     Running   0          10m
kube-controller-manager-k8s-master1   1/1     Running   0          10m
kube-flannel-ds-amd64-j4bp2           1/1     Running   0          4m4s
kube-proxy-svb9k                      1/1     Running   0          11m
kube-scheduler-k8s-master1            1/1     Running   0          10m

用node节点join新的 master

[root@k8s-node2 ~]# kubeadm join 192.168.32.29:6443 --token abcdef.0123456789abcdef     --discovery-token-ca-cert-hash sha256:799a1d11efdd0c092b8e3226e8d1c58f0ecaf3830e7cf587a13b0c4251fa7343
[preflight] Running pre-flight checks
	[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 19.03.9. Latest validated version: 18.09
error execution phase preflight: [preflight] Some fatal errors occurred:
	[ERROR FileAvailable--etc-kubernetes-kubelet.conf]: /etc/kubernetes/kubelet.conf already exists
	[ERROR FileAvailable--etc-kubernetes-bootstrap-kubelet.conf]: /etc/kubernetes/bootstrap-kubelet.conf already exists
	[ERROR Port-10250]: Port 10250 is in use
	[ERROR FileAvailable--etc-kubernetes-pki-ca.crt]: /etc/kubernetes/pki/ca.crt already exists
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`

出错了，因为之前已经已经join过，并且留下了config files，接下来删除旧的config files，并kill掉占用端口的进程

[root@k8s-node2 ~]# netstat -lnp|grep 10250
tcp6       0      0 :::10250                :::*                    LISTEN      8674/kubelet        
[root@k8s-node2 ~]# kill -9 8674
[root@k8s-node2 ~]# rm -rf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf etc/kubernetes/pki/ca.crt

执行kubeadm reset命令清除当前节点所有的配置

[root@k8s-node2 ~]# kubeadm reset
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
[preflight] Running pre-flight checks
W0524 15:40:46.463906   97562 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually.
For example:
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

这里又报了跟master一样的错，直接清除$HOME/.kube/config file

rm -rf $HOME/.kube/config

然后重新join master

[root@k8s-node2 ~]# kubeadm join 192.168.32.29:6443 --token abcdef.0123456789abcdef     --discovery-token-ca-cert-hash sha256:799a1d11efdd0c092b8e3226e8d1c58f0ecaf3830e7cf587a13b0c4251fa7343
[preflight] Running pre-flight checks
	[WARNING SystemVerification]: this Docker version is not on the list of validated versions: 19.03.9. Latest validated version: 18.09
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.15" ConfigMap in the kube-system namespace
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Activating the kubelet service
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

到这里node重新join master已经完成了，其他node的操作同理。
全部完成后，我们重新回到master看看集群的状态

[root@k8s-master1 ~]# kubectl get nodes
NAME          STATUS   ROLES    AGE     VERSION
k8s-master1   Ready    master   114m    v1.15.1
k8s-node1     Ready    <none>   10m     v1.15.1
k8s-node2     Ready    <none>   6m54s   v1.15.1

再看csr

[root@k8s-master1 ~]# kubectl get csr
NAME        AGE   REQUESTOR                 CONDITION
csr-l7dnl   39m   system:bootstrap:abcdef   Approved,Issued
csr-m5bwx   42m   system:bootstrap:abcdef   Approved,Issued

至此，更改所有hostname的踩坑之旅完成了。

IT三明治
关注
专栏目录
k8s高可用集群多个主节点_部署高可用k8s集群
weixin_39888049的博客
12-21 2629
高可用集群指 1个lb + 3个master(etcd) + n个node，生产环境都推荐这种安装方式新版的k8s，etcd节点已经可以完美和master节点共存于同一台服务器上；etcd有3种方式安装(独立安装、docker方式、k8s内部集成)；虽然k8s集成方式是官方推荐的，但是目前全是坑，这里还是采用独立安装方式。1.准备工作节点IP功能proxy192.168.0.10haproxyma...
k8s集群新增节点
wangqiubo2010的博客
02-07 7012
如何动态的为k8s集群增加worknode节点？本文将详细介绍，kubeadm搭建k8集群详见 https://blog.csdn.net/wangqiubo2010/article/details/101203625。 一、VMWare(xSphere)安装Censtos7虚拟机。 具体安装步骤 请谷歌百度。 二、确定外网、与K8S集群网络是通的。 #1、测试与K8S集群的网络是否会互通，例如master节点的ip地址为 172.16.8.31。 ping 172.16.8.31 #2、测试.
k8s---特殊操作（修改hostname）
weixin_45697293的博客
09-02 3431
在某些情况下需要将pod绑定至指定node节点，防止重启导致pod漂移到其他node节点。例如：将10.0.0.135修改未node-1。1、通过以下命令驱逐节点上pod应用。4、启动kubelete。例如：容器需要对外挂载。
k8s集群替换节点名称
qq_27501591的博客
06-20 698
k8s集群节点替换
The connection to the server localhost:8080 was refused - did you specify the right host or port?
最新发布
JCWang的博客
08-24 304
1.将master 节点中 /etc/kubernetes/admin,conf拷贝到需要运行的服务器的 /etc/kubernetes 目录中。如果在node节点上执行kubectl get node报。2.在对应的服务器上配置环境变量。
企业级大数据安全架构（三）修改集群节点hostname
01-11 1233
完成上面步骤之后如果修改了 repo 文件的主机名，那么需要验证一下或者直接通过 ambari 界面向导来安装某服务测试一下，或者直接在 shell 里面执行，yum install xxx，安装个东西测试一下，测试是否可以正常安装组件。hdp:是 ambari 创建 hdp 的集群名，可通过在Ambari页面的右上角admin用户下拉框的Manage Ambari进去，查看Cluster Information。停止 ambari-server 进程和所有节点上的 ambari-agent 进程。
Linux之为集群内的机器设定主机名
weixin_30847865的博客
03-21 196
作业二：为集群内的机器设定主机名，利用/etc/hosts文件来解析自己的集群中所有的主机名，相应的，集群的配置应该改成使用主机名的方式 1.主机信息配置并解析 [root@localhost ~]# vim /etc/hosts [root@localhost ~]# ping python [root@localhost ~]# vim /etc/hosts 注：因只有一个...
修改Kubernetes主节点（控制节点）名称
非法小恋
08-10 1891
1.修改物理机主机名 hostnamectl set-hostname <hostname> 2.修改 /etc/kubernetes/manifests 目录下的文件，将文件内容包含旧主机名的修改为新主机名，修改2处地方 cd /etc/kubernetes/manifests vi etcd.yaml 3.导出节点配置文件，编辑配置，把文件中旧主机名替换为新主机名，文件修改4处...
Kubeadm安装K8S单master节点集群
05-24
### Kubeadm安装K8S单Master节点集群详解 #### 一、集群环境规划与配置 根据提供的文档信息，我们了解到本次安装的目标是构建一个基于Kubeadm的Kubernetes (K8S) 单Master节点集群。该集群的具体规划如下： - **...
【kubernetes】二进制部署k8s集群之master节点和etcd数据库集群（上）
liu_xueyin的博客
02-22 1667
目录前言：关于整个k8s集群的主机规划以及本文部署架构步骤一：完成操作系统初始化配置步骤二：完成etcd集群部署关于etcd集群①准备签发证书环境②先完成单独一个节点的部署③通过部署好的etcd01节点 完成另外两个节点的部署拓展：了解etcdctl工具对etcd做增删改查拓展：通过etcdctl工具实现数据库的备份和恢复步骤三：完成docker引擎部署①完成docker部署②将docker的cgroup存储引擎修改为systemd步骤四：完成master组件部署①上传 master.zip 和 k8s-c
【云原生】二进制k8s集群（下）部署高可用master节点
qq_62462797的博客
12-10 2006
在上一篇文章中，就已经完成了二进制k8s集群部署的搭建，但是单机master并不适用于企业的实际运用（因为单机master中，仅仅只有一台master作为节点服务器的调度指挥，一旦宕机。就意味着整个集群的瘫痪，所以成熟的k8s的集群一定要考虑到master的高可用。）企业的运用一般至少存在两台master及其以上的部署，本次将根据前面的部署，再添加一台master（三个master或者更多，也可以根据本次添加步骤重复添加）。添加master后，我们会将借助keepalived+nginx的架构，来实现高可
K8S安装过程七：Kubernetes 节点配置调整
架构师实战感悟
11-28 1164
kubernetes 安装前修改操作系统配置信息
5.20集群搭建——MU
Lize_Mu的博客
05-20 914
目录 一、 修改主机名（三台） 3 首次切换到root用户：su 3 分别修改三台主机名为master，slave1，slave2 3 永久修改主机名 3 二、 配置host文件（三台） 3 查看各节点ip地址 3 将节点ip写进hosts文件：vi /etc/hosts 3 三、 关闭防火墙 3 关闭防火墙 3 查看防火墙状态 3 禁止启动，永久关闭防火墙 3 四、 时间同步 4 选择时区 4 选择TZ环境变量 4 下载ntp (三台机器) 4 设置master为时钟源（在master上进行操作） 4
k8s之master获取不到node信息
灬紫荆灬
11-06 4090
k8s集群master和node配置完成，并测试成功后，在master上执行kubectl get nodes获取不到node的信息：No resources found. 1.查看是否关闭了防火墙和防御机制 systemctl stop firewalld seteforce 0 2.修改apiserver配置文件 vim /etc/kubernetes/apiserver 找到 ”KUBE_ADMISSION_CONTROL="--admission_control=NamespaceLife
k8s技术遇到的问题1--No resources found.
weixin_44736359的博客
07-02 6001
[root@master ~]# kubectl get nodes No resources found. 解决方法： 所有节点： 1.关闭防火墙： systemctl stop firewalld systemctl disable firewalld 2.关闭selinux： sed -i 's/enforcing/disabled/' /etc/selinux/config setenforce 0 3.关闭swap： swapoff -a 临时 vim /etc/fstab 永
服务器错误统计
记忆的博客
08-15 534
服务器错误统计一、K8S证书（No resources found.）报错信息：kubectl get csr报错分析问题解决二、使用步骤1.引入库2.读入数据总结 一、K8S证书（No resources found.） 证书有效期，突然没有找到任何资源。 报错信息：kubectl get csr No resources found. 报错分析 master端接收不到node申请加入kubernetes的请求信息 问题解决 通过查看日志文件发现是kubelet没有启动成功，筛选kubelet发现没
k8s学习笔记-部署node节点
snipercai的博客
09-19 3057
主机列表 本次实验选择5台主机，3台作为master主机，2台作为node节点 节点ip OS版本 hostname -f 安装软件 192.168.0.1 RHEL7.4 k8s-master01 docker,etcd,flanneld,kube-apiserver,kube-controller-manager,kube-scheduler 1...
K8S查看pod日志遇到的问题及解决方案
技术分享，共同成长
11-20 2174
(2)、Namespace 错误：如果Pod存在于特定的命名空间（Namespace）中，但你没有指定正确的命名空间，就会导致这个错误。(1)、Pod 名称拼写错误：最常见的原因之一是Pod名称的拼写错误。K8s严格区分大小写，所以确保你输入的Pod名称是正确的。(3)、Pod 已被删除：如果你在尝试访问一个已经被删除的Pod，也会触发这个错误。(4)、API 服务器故障：偶尔，API服务器可能会出现故障或问题，导致它无法提供正确的信息。原因：查的是默认命名空间下的pod。查看k8s中特定pod的日志。
使用kubeadm搭建的k8s集群修改node节点主机名
weixin_44254035的博客
11-12 5214
刚用kubeadm搭完k8s集群，突然发现一个node节点忘记修改主机名了。删除节点，清空集群信息、修改主机名，重新加入到k8s集群，解决问题。 　　系统版本及内核版本如下 [root@master ~]# cat /etc/redhat-release CentOS Linux release 7.9.2009 (Core) [root@master ~]# uname -r 3.10.0-1062.el7.x86_64 操作步骤： 1.在master节点操作，查看节点数并删除node节点 [root
搭建非高可用K8s集群：节点规划与组件部署详解
首先，集群节点被划分为两类：master节点和slave节点。master节点负责集群的核心管理服务，如etcd、kube-apiserver、kube-controller-manager等，基础配置建议至少为2个CPU核心和4GB内存。两个slave节点用于运行工作...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

IT三明治

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值