ETCD3.5集群部署

1.192.168.10.20
2.192.168.10.30
3.192.168.10.33

节点192.168.10.20

tee /usr/lib/systemd/system/etcd.service <<-'EOF'
[Unit]
Description=Etcd Server
After=network.target[Service]
Type=notify
ExecStart=/usr/local/etcd-v3.5.2-linux-amd64/etcd \
--name=etcd-1 \
--data-dir=/data/etcd/default.etcd \
--listen-peer-urls=https://192.168.10.20:2380 \
--listen-client-urls=https://192.168.10.20:2379 \
--advertise-client-urls=https://192.168.10.20:2379,http://127.0.0.1:2379 \
--initial-advertise-peer-urls=https://192.168.10.20:2380 \
--initial-cluster=etcd-1=https://192.168.10.20:2380,etcd-2=https://192.168.10.30:2380,etcd-3=https://192.168.10.33:2380 \
--initial-cluster-token=etcd-cluster \
--initial-cluster-state=new \
--cert-file=/usr/local/tools/server.pem \
--key-file=/usr/local/tools/server-key.pem \
--peer-cert-file=/usr/local/tools/server.pem \
--peer-key-file=/usr/local/tools/server-key.pem \
--trusted-ca-file=/usr/local/tools/ca.pem \
--peer-trusted-ca-file=/usr/local/tools/ca.pem \
--logger=zap
Restart=on-failure
LimitNOFILE=65536[Install]
WantedBy=multi-user.target
EOF

节点192.168.10.30

tee /usr/lib/systemd/system/etcd.service <<-'EOF'
[Unit]
Description=Etcd Server
After=network.target[Service]
Type=notify
#EnvironmentFile=$ETCD_CONF
ExecStart=/usr/local/etcd-v3.5.2-linux-amd64/etcd \
--name=etcd-2 \
--data-dir=/data/etcd/default.etcd \
--listen-peer-urls=https://192.168.10.30:2380 \
--listen-client-urls=https://192.168.10.30:2379 \
--advertise-client-urls=https://192.168.10.30:2379,http://127.0.0.1:2379 \
--initial-advertise-peer-urls=https://192.168.10.30:2380 \
--initial-cluster=etcd-1=https://192.168.10.20:2380,etcd-2=https://192.168.10.30:2380,etcd-3=https://192.168.10.33:2380 \
--initial-cluster-token=etcd-cluster \
--initial-cluster-state=new \
--cert-file=/usr/local/tools/server.pem \
--key-file=/usr/local/tools/server-key.pem \
--peer-cert-file=/usr/local/tools/server.pem \
--peer-key-file=/usr/local/tools/server-key.pem \
--trusted-ca-file=/usr/local/tools/ca.pem \
--peer-trusted-ca-file=/usr/local/tools/ca.pem \
--logger=zap
Restart=on-failure
LimitNOFILE=65536[Install]
WantedBy=multi-user.target
EOF

节点192.168.10.33

tee /usr/lib/systemd/system/etcd.service <<-'EOF'
[Unit]
Description=Etcd Server
After=network.target[Service]
Type=notify
#EnvironmentFile=$ETCD_CONF
ExecStart=/usr/local/etcd-v3.5.2-linux-amd64/etcd \
--name=etcd-3 \
--data-dir=/data/etcd/default.etcd \
--listen-peer-urls=https://192.168.10.33:2380 \
--listen-client-urls=https://192.168.10.33:2379 \
--advertise-client-urls=https://192.168.10.33:2379,http://127.0.0.1:2379 \
--initial-advertise-peer-urls=https://192.168.10.33:2380 \
--initial-cluster=etcd-1=https://192.168.10.20:2380,etcd-2=https://192.168.10.30:2380,etcd-3=https://192.168.10.33:2380 \
--initial-cluster-token=etcd-cluster \
--initial-cluster-state=new \
--cert-file=/usr/local/tools/server.pem \
--key-file=/usr/local/tools/server-key.pem \
--peer-cert-file=/usr/local/tools/server.pem \
--peer-key-file=/usr/local/tools/server-key.pem \
--trusted-ca-file=/usr/local/tools/ca.pem \
--peer-trusted-ca-file=/usr/local/tools/ca.pem \
--logger=zap
Restart=on-failure
LimitNOFILE=65536[Install]
WantedBy=multi-user.target
EOF

启动

systemctl daemon-reload
systemctl enable etcd
systemctl start etcd
systemctl status etcd

客户端查询

etcdctl --endpoints="https://192.168.10.20:2379",https://192.168.10.30:2379,https://192.168.10.33:2379 \--cacert=/usr/local/tools/ca.pem \--cert=/usr/local/tools/server.pem \--key=/usr/local/tools/server-key.pem \endpoint status -w table

目前192.168.10.33节点为主

etcdctl --endpoints="https://192.168.10.20:2379",https://192.168.10.30:2379,https://192.168.10.33:2379 \--cacert=/usr/local/tools/ca.pem \--cert=/usr/local/tools/server.pem \--key=/usr/local/tools/server-key.pem \endpoint health

ETCD3.5集群部署相关推荐

etcd集群部署与遇到的坑(转)
原文 https://www.cnblogs.com/breg/p/5728237.html etcd集群部署与遇到的坑在k8s集群中使用了etcd作为数据中心,在实际操作中遇到了一些坑.今天记录一 ...
k8s集群部署之环境介绍与etcd数据库集群部署
角色 IP 组件配置 master-1 192.168.10.11 kube-apiserver kube-controller-manager kube-scheduler etcd 2c 2g ...
etcd集群部署与遇到的坑
2019独角兽企业重金招聘Python工程师标准>>> etcd集群部署与遇到的坑博客分类: 开源框架 etcd 在k8s集群中使用了etcd作为数据中心,在实际操作中遇到了一些坑 ...
【运维】K8S集群部署系列之ETCD集群搭建（四）
ETCD集群扩容和缩容本文将介绍生产环境下如何对ETCD集群进行扩容和缩容. 文章目录 ETCD集群扩容和缩容新节点环境准备(node3) 下载安装包并初始化环境网络准备生成`node3`对等 ...
k8s集群部署二进制(一)
部署一套完整的Kubernetes高可用集群(二进制) 一.前置知识点 1.1 生产环境可部署Kubernetes集群的两种方式目前生产部署Kubernetes集群主要有两种方式: kubeadm ...
Kylin集群部署和cube使用
Kylin集群部署和cube使用安装集群环境节点 Kylin节点模式 Ip 内存磁盘 Node1 All 192.167.71.11 2G 80G Node2 query 192.168.71. ...
堡垒机jumpserver集群部署
本文参考老广二次开发后的堡垒机部署方案,在此基础上进行集群部署,提高其可靠性.尽管国外已经有类似的功能的堡垒机的发布,但是还是要感谢老广在百忙之中开发出更加实用的堡垒机. 本文内容虽然亲测,但内容难免 ...
百度开源联邦学习框架 PaddleFL：简化大规模分布式集群部署
百度开源联邦学习框架 PaddleFL:简化大规模分布式集群部署作者 | 钰莹近两年,联邦学习技术发展迅速.作为分布式的机器学习范式,联邦学习能够有效解决数据孤岛问题,让参与方在不共享数据的基础上联 ...
手动安装K8s第三节：etcd集群部署
手动安装K8s第三节:etcd集群部署准备安装包 https://github.com/coreos/etcd 版本:3.2.18 wget https://github.com/coreos/et ...

ETCD3.5集群部署

ETCD3.5集群部署相关推荐

最新文章

热门文章