在一些企业的公有环境中可能无奈连贯内部的网络。如果要在这样的环境中部署Kubernetes集群,能够采集Kubernetes离线装置的形式进行部署。即:应用二进制安装包部署Kubernetes集群,采纳的版本是Kubernetes v1.18.20。

上面通过具体的步骤来演示如何应用二进制包部署三个节点的Kubernetes集群。

1. 部署ETCD

(1)从GitHub上下载ETCD的二进制安装包“etcd-v3.3.27-linux-amd64.tar.gz”。

(2)从cfssl官方网站上下载所须要的介质,并装置cfssl。

chmod +x cfssl_linux-amd64 cfssljson_linux-amd64mv cfssl_linux-amd64 /usr/local/bin/cfsslmv cfssljson_linux-amd64 /usr/local/bin/cfssljson
提醒: cfssl是一个命令行工具包,该工具包蕴含了运行一个认证核心所须要的全副性能。

(3)创立用于生成CA证书和私钥的配置文件,执行上面的命令:

mkdir -p /opt/ssl/etcdcd /opt/ssl/etcdcfssl print-defaults config > config.jsoncfssl print-defaults csr > csr.jsoncat > config.json <<EOF{  "signing": {    "default": {      "expiry": "87600h"    },    "profiles": {      "kubernetes": {        "usages": [            "signing",            "key encipherment",            "server auth",            "client auth"        ],        "expiry": "87600h"      }    }  }}EOFcat > csr.json <<EOF{   "CN": "etcd",   "key": {     "algo": "rsa",     "size": 2048   },   "names": [{    "C": "CN",    "ST": "BeiJing",    "L": "BeiJing",    "O": "k8s",    "OU": "System"   }]   }EOF

(4)生成CA证书和私钥。

cfssl gencert -initca csr.json | cfssljson -bare etcd

(5)在目录“/opt/ssl/etcd”下增加文件“etcd-csr.json”,该文件用于生成ETCD的证书和私钥,内容如下:

cat > etcd-csr.json <<EOF{  "CN": "etcd",  "hosts": [    "192.168.79.11"  ],  "key": {    "algo": "rsa",    "size": 2048  },  "names": [    {      "C": "CN",      "ST": "BeiJing",      "L": "BeiJing",      "O": "etcd",      "OU": "Etcd Security"    }  ]}EOF
提醒: 这里只部署了一个ETCD的节点。如果是部署ETCD集群,能够批改字段“hosts”增加多个ETCD节点即可。

(6)装置ETCD。

tar -zxvf etcd-v3.3.27-linux-amd64.tar.gzcd etcd-v3.3.27-linux-amd64cp etcd* /usr/local/binmkdir -p /opt/platform/etcd/

(7)编辑文件“/opt/platform/etcd/etcd.conf”增加ETCD的配置信息,内容如下:

ETCD_NAME=k8s-etcdETCD_DATA_DIR="/var/lib/etcd/k8s-etcd"ETCD_LISTEN_PEER_URLS="http://192.168.79.11:2380"ETCD_LISTEN_CLIENT_URLS="http://127.0.0.1:2379,http://192.168.79.11:2379"ETCD_INITIAL_ADVERTISE_PEER_URLS="http://192.168.79.11:2380"ETCD_INITIAL_CLUSTER="k8s-etcd=http://192.168.79.11:2380"ETCD_INITIAL_CLUSTER_STATE="new"ETCD_INITIAL_CLUSTER_TOKEN="etcd-test"ETCD_ADVERTISE_CLIENT_URLS="http://192.168.79.11:2379"

(8)将ETCD服务退出零碎服务中,编辑文件“/usr/lib/systemd/system/etcd.service”内容如下:

[Unit]Description=Etcd ServerAfter=network.targetAfter=network-online.targetWants=network-online.target[Service]Type=notifyEnvironmentFile=/opt/platform/etcd/etcd.confExecStart=/usr/local/bin/etcd \--cert-file=/opt/ssl/etcd/etcd.pem \--key-file=/opt/ssl/etcd/etcd-key.pem \--peer-cert-file=/opt/ssl/etcd/etcd.pem \--peer-key-file=/opt/ssl/etcd/etcd-key.pem \--trusted-ca-file=/opt/ssl/etcd/etcd.pem \--peer-trusted-ca-file=/opt/ssl/etcd/etcd.pemRestart=on-failureLimitNOFILE=65536[Install]WantedBy=multi-user.target

(9)创立ETCD的数据存储目录,而后启动ETCD服务。

mkdir -p /opt/platform/etcd/datachmod 755 /opt/platform/etcd/datasystemctl daemon-reloadsystemctl enable etcd.servicesystemctl start etcd.service

(10)验证ETCD的状态。

etcdctl cluster-health

输入信息如下:

member fd4d0bd2446259d9 is healthy: got healthy result from http://192.168.79.11:2379cluster is healthy

(11)查看ETCD的成员列表。

etcdctl member list

输入的信息如下:

fd4d0bd2446259d9: name=k8s-etcd peerURLs=http://192.168.79.11:2380 clientURLs=http://192.168.79.11:2379 isLeader=true
提醒: 因为是单节点的ETCD,因而这里只有一个成员信息。

(12)将ETCD的证书文件拷贝的node1和node2节点上。

cd /optscp -r ssl/ root@node1:/optscp -r ssl/ root@node2:/opt

2. 部署Flannel网络

(1)在master节点上写入调配的子网段到ETCD中供Flannel应用,执行命令:

etcdctl set /coreos.com/network/config '{ "Network": "172.17.0.0/16", "Backend": {"Type": "vxlan"}}'

(2)在master节点上查看写的Flannel子网信息,执行命令:

etcdctl get /coreos.com/network/config

输入的信息如下:

{ "Network": "172.17.0.0/16", "Backend": {"Type": "vxlan"}}

(3)在node1上解压flannel-v0.10.0-linux-amd64.tar.gz安装包,执行命令:

tar -zxvf flannel-v0.10.0-linux-amd64.tar.gz

(4)在node1上创立Kubernetes工作目录。

mkdir -p /opt/kubernetes/{cfg,bin,ssl}mv mk-docker-opts.sh flanneld /opt/kubernetes/bin/

(5)在node1上定义Flannel脚本文件“flannel.sh”,输出上面的内容:

#!/bin/bashETCD_ENDPOINTS=${1}cat <<EOF >/opt/kubernetes/cfg/flanneldFLANNEL_OPTIONS="--etcd-endpoints=${ETCD_ENDPOINTS} \-etcd-cafile=/opt/ssl/etcd/etcd.pem \-etcd-certfile=/opt/ssl/etcd/etcd.pem \-etcd-keyfile=/opt/ssl/etcd/etcd-key.pem"EOFcat <<EOF >/usr/lib/systemd/system/flanneld.service[Unit]Description=Flanneld overlay address etcd agentAfter=network-online.target network.targetBefore=docker.service[Service]Type=notifyEnvironmentFile=/opt/kubernetes/cfg/flanneldExecStart=/opt/kubernetes/bin/flanneld --ip-masq \$FLANNEL_OPTIONSExecStartPost=/opt/kubernetes/bin/mk-docker-opts.sh -k DOCKER_NETWORK_OPTIONS -d /run/flannel/subnet.envRestart=on-failure[Install]WantedBy=multi-user.targetEOFsystemctl daemon-reloadsystemctl enable flanneldsystemctl restart flanneld

(6)在node1节点上开启Flannel网络性能,执行命令:

bash flannel.sh http://192.168.79.11:2379
提醒: 这里指定了在master节点上部署的ETCD地址。

(7)在node1节点上查看Flannel网络的状态,执行命令:

systemctl status flanneld

输入的信息如下:

flanneld.service - Flanneld overlay address etcd agent Loaded: loaded (/usr/lib/systemd/system/flanneld.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2022-02-08 22:30:46 CST; 6s ago

(8)在node1节点上批改文件“/usr/lib/systemd/system/docker.service”配置node1节点上的Docker连贯Flannel网络,在文件中减少上面的一行:

... ...EnvironmentFile=/run/flannel/subnet.env... ...

(9)在node1节点上重启Docker服务。

systemctl daemon-reload systemctl restart docker.service 

(10)查看node1节点上的Flannel网络信息,如图13-3所示:

ifconfig

(11)在node2节点上配置Flannel网络,反复第3步到第10步。

3. 部署Master节点

(1)创立Kubernetes集群证书目录。

mkdir -p /opt/ssl/k8scd /opt/ssl/k8s

(2)创立脚本文件“k8s-cert.sh”用于生成Kubernetes集群的证书,在脚本中输出上面的内容:

cat > ca-config.json <<EOF{  "signing": {    "default": {      "expiry": "87600h"    },    "profiles": {      "kubernetes": {        "usages": [            "signing",            "key encipherment",            "server auth",            "client auth"        ],        "expiry": "87600h"      }    }  }}EOFcat > ca-csr.json <<EOF{   "CN": "kubernetes",   "key": {     "algo": "rsa",     "size": 2048   },   "names": [{    "C": "CN",    "ST": "BeiJing",    "L": "BeiJing",    "O": "k8s",    "OU": "System"   }]   }EOFcfssl gencert -initca ca-csr.json | cfssljson -bare cacat >server-csr.json<<EOF{  "CN": "kubernetes",  "hosts": [     "192.168.79.11",     "127.0.0.1",     "kubernetes",     "kubernetes.default",     "kubernetes.default.svc",     "kubernetes.default.svc.cluster",     "kubernetes.default.svc.cluster.local"  ],  "key": {    "algo": "rsa",    "size": 2048  },  "names": [    {      "C": "CN",      "L": "BeiJing",      "ST": "BeiJing",      "O": "system:masters",      "OU": "System"    }  ]}EOFcfssl gencert -ca=ca.pem -ca-key=ca-key.pem \-config=ca-config.json -profile=kubernetes \server-csr.json | cfssljson -bare servercat >admin-csr.json <<EOF{  "CN": "admin",  "hosts": [],  "key": {    "algo": "rsa",    "size": 2048  },  "names": [    {      "C": "CN",      "L": "BeiJing",      "ST": "BeiJing",      "O": "system:masters",      "OU": "System"    }  ]}EOFcfssl gencert -ca=ca.pem -ca-key=ca-key.pem \-config=ca-config.json -profile=kubernetes \admin-csr.json | cfssljson -bare admincat > kube-proxy-csr.json <<EOF{  "CN": "system:kube-proxy",  "hosts": [],  "key": {    "algo": "rsa",    "size": 2048  },  "names": [    {      "C": "CN",      "L": "BeiJing",      "ST": "BeiJing",      "O": "k8s",      "OU": "System"    }  ]}EOFcfssl gencert -ca=ca.pem -ca-key=ca-key.pem \-config=ca-config.json -profile=kubernetes \kube-proxy-csr.json | cfssljson -bare kube-proxy

(3)执行脚本文件“k8s-cert.sh”。

bash k8s-cert.sh

(4)拷贝证书。

mkdir -p /opt/kubernetes/ssl/mkdir -p /opt/kubernetes/logs/cp ca*pem server*pem /opt/kubernetes/ssl/

(5))解压kubernetes压缩包

tar -zxvf kubernetes-server-linux-amd64.tar.gz 

(6)复制要害命令文件

mkdir -p /opt/kubernetes/bin/cd kubernetes/server/bin/cp kube-apiserver kube-scheduler kube-controller-manager \   /opt/kubernetes/bincp kubectl /usr/local/bin/

(7)随机生成序列号。

mkdir -p /opt/kubernetes/cfghead -c 16 /dev/urandom | od -An -t x | tr -d ' '

输入内容如下:

05cd8031b0c415de2f062503b0cd4ee6

(8)创立“/opt/kubernetes/cfg/token.csv”文件,输出上面的内容:

05cd8031b0c415de2f062503b0cd4ee6,kubelet-bootstrap,10001,"system:node-bootstrapper"

(9)创立API Server的配置文件“/opt/kubernetes/cfg/kube-apiserver.conf”,输出上面的内容:

KUBE_APISERVER_OPTS="--logtostderr=false \--v=2 \--log-dir=/opt/kubernetes/logs \--etcd-servers=http://192.168.79.11:2379 \--bind-address=192.168.79.11 \--secure-port=6443 \--advertise-address=192.168.79.11 \--allow-privileged=true \--service-cluster-ip-range=10.0.0.0/24 \--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \--authorization-mode=RBAC,Node \--enable-bootstrap-token-auth=true \--token-auth-file=/opt/kubernetes/cfg/token.csv \--service-node-port-range=30000-32767 \--kubelet-client-certificate=/opt/kubernetes/ssl/server.pem \--kubelet-client-key=/opt/kubernetes/ssl/server-key.pem \--tls-cert-file=/opt/kubernetes/ssl/server.pem \--tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \--client-ca-file=/opt/kubernetes/ssl/ca.pem \--service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \--etcd-cafile=/opt/ssl/etcd/etcd.pem \--etcd-certfile=/opt/ssl/etcd/etcd.pem \--etcd-keyfile=/opt/ssl/etcd/etcd-key.pem \--audit-log-maxage=30 \--audit-log-maxbackup=3 \--audit-log-maxsize=100 \--audit-log-path=/opt/kubernetes/logs/k8s-audit.log"

(10)应用零碎的systemd来治理API Server,执行命令:

cat > /usr/lib/systemd/system/kube-apiserver.service << EOF[Unit]Description=Kubernetes API ServerDocumentation=https://github.com/kubernetes/kubernetes[Service]EnvironmentFile=/opt/kubernetes/cfg/kube-apiserver.confExecStart=/opt/kubernetes/bin/kube-apiserver \$KUBE_APISERVER_OPTSRestart=on-failure[Install]WantedBy=multi-user.targetEOF

(11)启动API Server。

systemctl daemon-reloadsystemctl start kube-apiserversystemctl enable kube-apiserver

(12)查看API Server的状态。

systemctl status kube-apiserver.service

输入的信息如下:

kube-apiserver.service - Kubernetes API ServerLoaded: loaded (/usr/lib/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled)Active: active (running) since Tue 2022-02-08 21:11:47 CST; 24min ago

(13)查看监听的端口6433和端口8080信息,如图13-4所示。

netstat -ntap | grep 6443netstat -ntap | grep 8080

(14)受权kubelet-bootstrap用户容许申请证书。

kubectl create clusterrolebinding kubelet-bootstrap \--clusterrole=system:node-bootstrapper \--user=kubelet-bootstrap

(15)创立kube-controller-manager的配置文件,执行命令:

cat > /opt/kubernetes/cfg/kube-controller-manager.conf << EOFKUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=false \--v=2 \--log-dir=/opt/kubernetes/logs \--leader-elect=true \--master=127.0.0.1:8080 \--bind-address=127.0.0.1 \--allocate-node-cidrs=true \--cluster-cidr=10.244.0.0/16 \--service-cluster-ip-range=10.0.0.0/24 \--cluster-signing-cert-file=/opt/kubernetes/ssl/ca.pem \--cluster-signing-key-file=/opt/kubernetes/ssl/ca-key.pem  \--root-ca-file=/opt/kubernetes/ssl/ca.pem \--service-account-private-key-file=/opt/kubernetes/ssl/ca-key.pem \--experimental-cluster-signing-duration=87600h0m0s"EOF

(16)应用systemd服务来治理kube-controller-manager,执行命令

cat > /usr/lib/systemd/system/kube-controller-manager.service << EOF[Unit]Description=Kubernetes Controller ManagerDocumentation=https://github.com/kubernetes/kubernetes[Service]EnvironmentFile=/opt/kubernetes/cfg/kube-controller-manager.confExecStart=/opt/kubernetes/bin/kube-controller-manager \$KUBE_CONTROLLER_MANAGER_OPTSRestart=on-failure[Install]WantedBy=multi-user.targetEOF

(17)启动kube-controller-manager。

systemctl daemon-reloadsystemctl start kube-controller-managersystemctl enable kube-controller-manager

(18)查看kube-controller-manager的状态。

systemctl status kube-controller-manager

输入的信息如下:

kube-controller-manager.service - Kubernetes Controller ManagerLoaded: loaded (/usr/lib/systemd/system/kube-controller-manager.service; enabled; vendor preset: disabled)Active: active (running) since Tue 2022-02-08 20:42:08 CST; 1h 2min ago

(19)创立kube-scheduler的配置文件,执行命令:

cat > /opt/kubernetes/cfg/kube-scheduler.conf << EOFKUBE_SCHEDULER_OPTS="--logtostderr=false \--v=2 \--log-dir=/opt/kubernetes/logs \--leader-elect \--master=127.0.0.1:8080 \--bind-address=127.0.0.1"EOF

(20)应用systemd服务来治理kube-scheduler,执行命令:

cat > /usr/lib/systemd/system/kube-scheduler.service << EOF[Unit]Description=Kubernetes SchedulerDocumentation=https://github.com/kubernetes/kubernetes[Service]EnvironmentFile=/opt/kubernetes/cfg/kube-scheduler.confExecStart=/opt/kubernetes/bin/kube-scheduler \$KUBE_SCHEDULER_OPTSRestart=on-failure[Install]WantedBy=multi-user.targetEOF

(21)启动kube-scheduler。

systemctl daemon-reloadsystemctl start kube-schedulersystemctl enable kube-scheduler

(22)查看kube-scheduler的状态。

systemctl status kube-scheduler.service

输入的信息如下:

kube-scheduler.service - Kubernetes Scheduler Loaded: loaded (/usr/lib/systemd/system/kube-scheduler.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2022-02-08 20:43:01 CST; 1h 8min ago

(23)查看master节点的状态信息。

kubectl get cs

输入的信息如下:

NAME                   STATUS    MESSAGE             ERRORetcd-0                 Healthy   {"health":"true"}   controller-manager     Healthy   ok                  scheduler              Healthy   ok   

4. 部署Node节点

(1)在master节点上创立脚本文件“kubeconfig”,输出上面的内容:

APISERVER=${1}SSL_DIR=${2} # 创立kubelet bootstrapping kubeconfig export KUBE_APISERVER="https://$APISERVER:6443" # 设置集群参数kubectl config set-cluster kubernetes \  --certificate-authority=$SSL_DIR/ca.pem \  --embed-certs=true \  --server=${KUBE_APISERVER} \  --kubeconfig=bootstrap.kubeconfig # 设置客户端认证参数# 留神这里的token ID须要与token.csv文件中的ID统一。kubectl config set-credentials kubelet-bootstrap \  --token=05cd8031b0c415de2f062503b0cd4ee6 \  --kubeconfig=bootstrap.kubeconfig # 设置上下文参数kubectl config set-context default \  --cluster=kubernetes \  --user=kubelet-bootstrap \  --kubeconfig=bootstrap.kubeconfig # 设置默认上下文kubectl config use-context default --kubeconfig=bootstrap.kubeconfig #---------------------- # 创立kube-proxy kubeconfig文件 kubectl config set-cluster kubernetes \  --certificate-authority=$SSL_DIR/ca.pem \  --embed-certs=true \  --server=${KUBE_APISERVER} \  --kubeconfig=kube-proxy.kubeconfig kubectl config set-credentials kube-proxy \  --client-certificate=$SSL_DIR/kube-proxy.pem \  --client-key=$SSL_DIR/kube-proxy-key.pem \  --embed-certs=true \  --kubeconfig=kube-proxy.kubeconfig kubectl config set-context default \  --cluster=kubernetes \  --user=kube-proxy \  --kubeconfig=kube-proxy.kubeconfig kubectl config use-context default --kubeconfig=kube-proxy.kubeconfig

(2)执行脚本文件“kubeconfig”。

bash kubeconfig 192.168.79.11 /opt/ssl/k8s/

输入的信息如下:

Cluster "kubernetes" set.User "kubelet-bootstrap" set.Context "default" created.Switched to context "default".Cluster "kubernetes" set.User "kube-proxy" set.Context "default" created.Switched to context "default".

(3)将master节点上生成的配置文件拷贝到node1节点和node2节点。

scp bootstrap.kubeconfig kube-proxy.kubeconfig \root@node1:/opt/kubernetes/cfg/scp bootstrap.kubeconfig kube-proxy.kubeconfig \root@node2:/opt/kubernetes/cfg/

(4)在node1节点上解压文件“kubernetes-node-linux-amd64.tar.gz”。

tar -zxvf kubernetes-node-linux-amd64.tar.gz

(5)在node1节点上将kubelet和kube-proxy复制到目录“/opt/kubernetes/bin/”下。

cd kubernetes/node/bin/cp kubelet kube-proxy /opt/kubernetes/bin/

(6)在node1节点上创立脚本文件“kubelet.sh”,输出上面的内容:

#!/bin/bashNODE_ADDRESS=$1DNS_SERVER_IP=${2:-"10.0.0.2"}cat <<EOF >/opt/kubernetes/cfg/kubeletKUBELET_OPTS="--logtostderr=true \\--v=4 \\--hostname-override=${NODE_ADDRESS} \\--kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \\--bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \\--config=/opt/kubernetes/cfg/kubelet.config \\--cert-dir=/opt/kubernetes/ssl \\--pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0"EOFcat <<EOF >/opt/kubernetes/cfg/kubelet.configkind: KubeletConfigurationapiVersion: kubelet.config.k8s.io/v1beta1address: ${NODE_ADDRESS}port: 10250readOnlyPort: 10255cgroupDriver: systemdclusterDNS:- ${DNS_SERVER_IP} clusterDomain: cluster.local.failSwapOn: falseauthentication:  anonymous:    enabled: trueEOFcat <<EOF >/usr/lib/systemd/system/kubelet.service[Unit]Description=Kubernetes KubeletAfter=docker.serviceRequires=docker.service[Service]EnvironmentFile=/opt/kubernetes/cfg/kubeletExecStart=/opt/kubernetes/bin/kubelet \$KUBELET_OPTSRestart=on-failureKillMode=process[Install]WantedBy=multi-user.targetEOFsystemctl daemon-reloadsystemctl enable kubeletsystemctl restart kubelet

(7)在node1节点上执行脚本文件“kubelet.sh”。

bash kubelet.sh 192.168.79.12
提醒: 这里指定的node1节点的IP地址。

(8)在node1节点上查看Kubelet的状态。

systemctl status kubelet

输入的信息如下:

kubelet.service - Kubernetes Kubelet Loaded: loaded
(/usr/lib/systemd/system/kubelet.service; enabled; vendor preset:
disabled) Active: active (running) since Tue 2022-02-08 23:23:52 CST;
3min 18s ago

(9)在node1节点上创立脚本文件“proxy.sh”,输出上面的内容

#!/bin/bashNODE_ADDRESS=$1cat <<EOF >/opt/kubernetes/cfg/kube-proxyKUBE_PROXY_OPTS="--logtostderr=true \\--v=4 \\--hostname-override=${NODE_ADDRESS} \\--cluster-cidr=10.0.0.0/24 \\--proxy-mode=ipvs \\--kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig"EOFcat <<EOF >/usr/lib/systemd/system/kube-proxy.service[Unit]Description=Kubernetes ProxyAfter=network.target[Service]EnvironmentFile=-/opt/kubernetes/cfg/kube-proxyExecStart=/opt/kubernetes/bin/kube-proxy \$KUBE_PROXY_OPTSRestart=on-failure[Install]WantedBy=multi-user.targetEOFsystemctl daemon-reloadsystemctl enable kube-proxysystemctl restart kube-proxy

(10)在node1节点上执行脚本文件“proxy.sh”。

bash proxy.sh 192.168.79.12

(11)在node1节点上查看kube-proxy的状态。

systemctl status kube-proxy.service

输入的信息如下:

kube-proxy.service - Kubernetes Proxy Loaded: loaded (/usr/lib/systemd/system/kube-proxy.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2022-02-08 23:30:51 CST; 9s ago

(12)在master节点上查看node1节点退出集群的申请信息,执行命令:

kubectl get csr

输入的信息如下:

NAME                                                 ... CONDITIONnode-csr-Qc2wKIo6AIWh6AXKW6tNwAvUqpxEIXFPHkkIe1jzSBE ... Pending

(13)在master节点上批准node1节点的申请,执行命令:

kubectl certificate approve \node-csr-Qc2wKIo6AIWh6AXKW6tNwAvUqpxEIXFPHkkIe1jzSBE

(14)在master节点上查看Kubernetes集群中的节点信息,执行命令:

kubectl get node

输入的信息如下:

NAME            STATUS   ROLES    AGE   VERSION192.168.79.12   Ready    <none>   85s   v1.18.20
提醒: 这时候node1节点曾经胜利退出了Kubernetes集群中。

(15)在node2节点上反复第4步到第14步,依照同样的办法把node2节点退出集群。
(16)在master节点上查看Kubernetes集群中的节点信息,执行命令:

kubectl get node

输入的信息如下:

NAME             STATUS   ROLES     AGE     VERSION192.168.79.12   Ready    <none>   5m47s   v1.18.20192.168.79.13   Ready    <none>   11s     v1.18.20

至此便胜利应用二进制包部署了三个节点的Kubernetes集群。