root@k8s-master1 \~\]# kubectl get cs NAME STATUS MESSAGE ERROR controller-manager Healthy ok scheduler Healthy ok etcd-1 Healthy {"health":"true"} etcd-0 Healthy {"health":"true"} etcd-2 Unhealthy HTTP probe failed with statuscode: 503 ETCDCTL_API=3 /opt/etcd/bin/etcdctl --cacert=/opt/etcd/ssl/ca.pem --cert=/opt/etcd/ssl/server.pem --key=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.233.91:2379,https://192.168.233.93:2379,https://192.168.233.94:2379" endpoint health --write-out=table 1.将有故障的etcd节点remove出集群: ETCDCTL_API=3 /opt/etcd/bin/etcdctl --cacert=/opt/etcd/ssl/ca.pem --cert=/opt/etcd/ssl/server.pem --key=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.233.91:2379,https://192.168.233.93:2379,https://192.168.233.94:2379" --write-out=table member list cf4f326398a30bd2 86ec40d44e54cf0a /opt/etcd/bin/etcdctl --cacert=/opt/etcd/ssl/ca.pem --cert=/opt/etcd/ssl/server.pem --key=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.233.91:2379,https://192.168.233.93:2379,https://192.168.233.94:2379" member remove 故障节点的id 2、来到故障节点 rm -rf /var/lib/etcd/default.etcd/member/ 修改etcd配置文件,将下面new修改为: vim /opt/etcd/cfg/etcd 修改前: ETCD_INITIAL_CLUSTER_STATE="new" 修改后: ETCD_INITIAL_CLUSTER_STATE="existing" 3、重新加入etcd集群: /opt/etcd/bin/etcdctl --cacert=/opt/etcd/ssl/ca.pem --cert=/opt/etcd/ssl/server.pem --key=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.233.91:2379,https://192.168.233.93:2379,https://192.168.233.94:2379" member add etcd-2 --peer-urls=https://192.168.233.94:2380 4、重启etcd故障节点
相关推荐
SilentSamsara12 小时前
存储卷体系:EmptyDir/HostPath/PV/PVC/StorageClass 的选型决策树王的宝库12 小时前
【K8s】集群安全机制(二):授权(Authorization)详解与实战东北甜妹15 小时前
Docker 容器故障排查Shining059616 小时前
QEMU 编译开发环境搭建匀泪1 天前
云原生(Kubernetes service微服务)倔强的胖蚂蚁1 天前
Ollama Modelfile 配置文件 全指南AutoMQ2 天前
AWS 新发布的 S3 Files 适合作为 Kafka 的存储吗?MY_TEUCK2 天前
从零开始:使用Sealos Devbox快速搭建云原生开发环境没有口袋啦2 天前
《基于 GitOps 理念的企业级自动化 CI/CD 流水线》柯西劝我别收敛2 天前
Koordinator-Scheduler 调度器源码解析