本文共 3703 字,大约阅读时间需要 12 分钟。
master
节点需要etcd
(复用master节点,也可以独立三节点部署etcd,只要kubernetes集群可以访问即可)k8s-01:~ # cd /opt/k8s/packages/k8s-01:/opt/k8s/packages # wget https://github.com/etcd-io/etcd/releases/download/v3.4.12/etcd-v3.4.12-linux-amd64.tar.gzk8s-01:/opt/k8s/packages # tar xf etcd-v3.4.12-linux-amd64.tar.gz
k8s-01:~ # cd /opt/k8s/sslk8s-01:/opt/k8s/ssl # cat > etcd-csr.json <
host字段
指定授权使用该证书的etcd节点IP
或域名列表
,需要将etcd集群的3个节点
都添加其中k8s-01:/opt/k8s/ssl # cfssl gencert -ca=/opt/k8s/ssl/ca.pem \-ca-key=/opt/k8s/ssl/ca-key.pem \-config=/opt/k8s/ssl/ca-config.json \-profile=kubernetes etcd-csr.json | cfssljson -bare etcd
k8s-01:~ # cd /opt/k8s/conf/k8s-01:/opt/k8s/conf # source /opt/k8s/bin/k8s-env.shk8s-01:/opt/k8s/conf # cat > etcd.service.template <
WorkDirectory
、--data-dir
指定etcd工作目录和数据存储为${ETCD_DATA_DIR},需要在启动前创建这个目录 (后面会有创建步骤)--wal-dir
指定wal目录,为了提高性能,一般使用SSD和–data-dir不同的盘--name
指定节点名称,当–initial-cluster-state值为new时,–name的参数值必须位于–initial-cluster列表中--cert-file
、--key-file
etcd server与client通信时使用的证书和私钥--trusted-ca-file
签名client证书的CA证书,用于验证client证书--peer-cert-file
、--peer-key-file
etcd与peer通信使用的证书和私钥--peer-trusted-ca-file
签名peer证书的CA证书,用于验证peer证书#!/usr/bin/env bashsource /opt/k8s/bin/k8s-env.shfor (( i=0; i < 3; i++ ))do sed -e "s/##NODE_NAME##/${MASTER_NAMES[i]}/" \ -e "s/##NODE_IP##/${ETCD_IPS[i]}/" \ /opt/k8s/conf/etcd.service.template > /opt/k8s/conf/etcd-${ETCD_IPS[i]}.servicedonefor host in ${ETCD_IPS[@]}do printf "\e[1;34m${host}\e[0m\n" scp /opt/k8s/packages/etcd-v3.4.12-linux-amd64/etcd* ${host}:/opt/k8s/bin/ scp /opt/k8s/conf/etcd-${host}.service ${host}:/etc/systemd/system/etcd.service scp /opt/k8s/ssl/etcd*.pem ${host}:/etc/etcd/cert/done
#!/usr/bin/env bashsource /opt/k8s/bin/k8s-env.shfor host in ${ETCD_IPS[@]}do printf "\e[1;34m${host}\e[0m\n" ssh root@${host} "mkdir -p ${ETCD_DATA_DIR} ${ETCD_WAL_DIR}" ssh root@${host} "chmod 700 ${ETCD_DATA_DIR}" ssh root@${host} "systemctl daemon-reload && \ systemctl enable etcd && \ systemctl restart etcd && \ systemctl status etcd | grep Active"done
192.168.72.39Created symlink from /etc/systemd/system/multi-user.target.wants/etcd.service to /etc/systemd/system/etcd.service.Job for etcd.service failed because a timeout was exceeded. See "systemctl status etcd.service" and "journalctl -xe" for details.192.168.72.40Created symlink from /etc/systemd/system/multi-user.target.wants/etcd.service to /etc/systemd/system/etcd.service. Active: active (running) since Sat 2021-02-13 00:27:24 CST; 16ms ago192.168.72.41Created symlink from /etc/systemd/system/multi-user.target.wants/etcd.service to /etc/systemd/system/etcd.service. Active: active (running) since Sat 2021-02-13 00:27:25 CST; 6ms ago
#!/usr/bin/env bashsource /opt/k8s/bin/k8s-env.shfor host in ${ETCD_IPS[@]}do printf "\e[1;34m${host}\e[0m\n" ETCDCTL_API=3 /opt/k8s/bin/etcdctl \ --endpoints=https://${host}:2379 \ --cacert=/etc/kubernetes/cert/ca.pem \ --cert=/etc/etcd/cert/etcd.pem \ --key=/etc/etcd/cert/etcd-key.pem endpoint healthdone
successfully committed proposal
则表示集群正常192.168.72.39https://192.168.72.39:2379 is healthy: successfully committed proposal: took = 9.402229ms192.168.72.40https://192.168.72.40:2379 is healthy: successfully committed proposal: took = 10.247073ms192.168.72.41https://192.168.72.41:2379 is healthy: successfully committed proposal: took = 11.01422ms
转载地址:http://zkuh.baihongyu.com/