文章目錄
一、K8s單master羣集環境介紹
羣集拓撲圖:
服務器規劃:
自籤SSL證書:
二、Master節點組件介紹
1、kube-apiserver
:是集羣的統一入口,各組件協調者,所有對象資源的增刪改查和監聽操 作都交給 APIServer 處理後再提交給 Etcd 存儲;
2、kube-controller-manager
:處理羣集中常規後臺任務,一個資源對應一個控制器,而 controller-manager 就是負責管理這些控制器的;
3、kube-scheduler
:根據調度算法爲新創建的 Pod 選擇一個 Node 節點,可以任意部署,可以部署在同一個節點上,也可以部署在不同節點上。
4、kube-bootstrap
:用戶綁定到系統羣集的角色,用於master控制node節點,在master節點上創建,推送給node節點,node節點使用該用戶像master發送頒發證書請求
三、node節點組件介紹
1、kubelet
:是master在node節點上的agent,可以管理本機運行容器的生命週期,例如創建容器、Pod掛載數據卷、下載secret、獲取容器和節點狀態等工作,kubelet 將每個 Pod轉換成一組容器。
2、kube-proxy
:在 node節點上實現 Pod網絡代理,維護網絡規劃和四層負載均衡工作。
3、docker
:容器運行環境
四、實驗步驟
部署etcd羣集----》》部署flannel容器羣集網絡----》》部署master節點----》》部署node節點
五、Etcd羣集部署
參考上篇博客ETCD羣集,點此跳
六、Flannel網絡部署
- Flannel是Overlay網絡的一種,也是將源數據封裝在另一種網絡包裏面進行路由轉發和通信;
- Flannel通過給每臺宿主機分配一個子網的方式爲容器提供虛擬網絡,它基於Linux TUN/TAP,使用UDP/VXLAN封裝IP包來創建overlay網絡,並藉助etcd(也支持kubernetes)維護網絡的分配情況。
- 在2個不同子網的容器通信時將數據流量封裝在UDP協議中,外層又加了一層ip,(兩層ip)內部ip是pod的ip,中間承載協議是UDP,外部是node真實網卡地址
flannel部署步驟如下:
- 在msater節點中爲flannel分配子網,並寫入etcd數據庫中
[root@k8s_master ~]# /opt/etcd/bin/etcdctl --ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.142.220:2379,https://192.168.5.20:2379,https://192.168.5.30:2379" set /coreos.com/network/config '{"Network":"172.17.0.0/16","Backend":{"Type":"vxlan"}}'
-
2個node節點上安裝docker引擎
Docker-ce版部署,點此跳 -
2個node節點解壓安裝flannel二進制源碼包,源碼包下載地址:https://github.com/coreos/flannel/releases
tar zxvf flannel-v0.10.0-linux-amd64.tar.gz
- 2個node節點創建K8S工作目錄便於管理
##創建目錄
mkdir -p /opt/kubernetes/{cfg,ssl,bin}
##移動flanneld到工作目錄
mv flanneld mk-docker-opts.sh /opt/kubernetes/bin/
- 2個node節點更改flannel配置文件
cat <<EOF >/opt/kubernetes/cfg/flanneld.cfg
FLANNEL_OPTIONS="--etcd-endpoints=https://192.168.5.10:2379,https://192.168.5.20:2379,https://192.168.5.30:2379 \
-etcd-cafile=/opt/etcd/ssl/ca.pem \
-etcd-certfile=/opt/etcd/ssl/server.pem \
-etcd-keyfile=/opt/etcd/ssl/server-key.pem
EOF
- 2個node節點編寫flannel的啓動腳本
cat <<EOF >/usr/lib/systemd/system/flanneld.service
[Unit]
Description=Flanneld overlay address etcd agent
After=network-online.target network.target
Before=docker.service
[Service]
Type=notify
EnvironmentFile=/opt/kubernetes/cfg/flanneld.cfg
ExecStart=/opt/kubernetes/bin/flanneld --ip-masq \$FLANNEL_OPTIONS
ExecStartPost=/opt/kubernetes/bin/mk-docker-opts.sh -k DOCKER_NETWORK_OPTIONS -d /run/flannel/subnet.env
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
- 2個node節點啓動flannel服務
chmod +x /usr/lib/systemd/system/flanneld.service
systemctl start flanneld.service
systemctl enable flanneld.service
systemctl status flanneld.service
- 配置docker連接flannel
vim /usr/lib/systemd/system/docker.service
##13行添加
EnvironmentFile=/run/flannel/subnet.env
##修改14行
ExecStart=/usr/bin/dockerd $DOCKER_NETWORK_OPTIONS(添加該變量,加入flannel網絡中) -H fd:// --containerd=/run/containerd/containerd.sock
- 2個node節點檢查自身分配的子網段
cat /run/flannel/subnet.env
- 2個node節點重啓容器使配置文件生效
systemctl daemon-reload
systemctl restart docker
- 檢查flannel網絡互通性,2個節點都安裝centos7容器,進入容器使用ping指令檢查網絡
##2個節點都安裝容器
docker run -it centos:7 /bin/bash
yum install -y net-tools
##node1容器ip
[root@ae25456150cb /]# ifconfig | sed -n '2p'|awk '{print $2}'
172.17.53.2
##noede2容器ip
[root@5f9a085e6bbd /]# ifconfig | sed -n '2p'|awk '{print $2}'
172.17.20.2
###測試聯通性
[root@ae25456150cb /]# ping 172.17.20.2
PING 172.17.20.2 (172.17.20.2) 56(84) bytes of data.
64 bytes from 172.17.20.2: icmp_seq=1 ttl=62 time=1.12 ms
64 bytes from 172.17.20.2: icmp_seq=2 ttl=62 time=1.04 ms
64 bytes from 172.17.20.2: icmp_seq=3 ttl=62 time=1.09 ms
^C
--- 172.17.20.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 1.041/1.088/1.128/0.035 ms
七、Master節點部署
- 在master節點上,生成apiserver組件證書
##創建證書存放目錄
[root@k8s_master ~]# mkdir /root/k8s-cert
[root@k8s_master ~]# cd /root/k8s-cert
##創建證書生成腳本
[root@k8s_master k8s-cert]# vi k8s-cert.sh
###添加以下內容
cat > ca-config.json <<EOF
{
"signing": {
"default": {
"expiry": "87600h"
},
"profiles": {
"kubernetes": {
"expiry": "87600h",
"usages": [
"signing",
"key encipherment",
"server auth",
"client auth"
]
}
}
}
}
EOF
cat > ca-csr.json <<EOF
{
"CN": "kubernetes",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "Beijing",
"ST": "Beijing",
"O": "k8s",
"OU": "System"
}
]
}
EOF
cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
#-----------------------
cat > server-csr.json <<EOF
{
"CN": "kubernetes",
"hosts": [
"10.0.0.1",
"127.0.0.1",
"192.168.5.10",
"192.168.5.11",
"192.168.5.100",
"192.168.5.12",
"192.168.5.13",
"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": "k8s",
"OU": "System"
}
]
}
EOF
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes server-csr.json | cfssljson -bare server
#-----------------------
cat > admin-csr.json <<EOF
{
"CN": "admin",
"hosts": [],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "BeiJing",
"ST": "BeiJing",
"O": "system:masters",
"OU": "System"
}
]
}
EOF
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes admin-csr.json | cfssljson -bare admin
#-----------------------
cat > 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"
}
]
}
EOF
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes kube-proxy-csr.json | cfssljson -bare kube-proxy
###執行腳本
[root@k8s_master k8s-cert]# bash k8s-cert.sh
##此時會生成8個證書
[root@k8s_master k8s-cert]# ls *.pem
admin-key.pem admin.pem ca-key.pem ca.pem kube-proxy-key.pem kube-proxy.pem server-key.pem server.pem
- 創建k8s工作目錄 ,便於管理
[root@k8s_master k8s-cert]# mkdir -p /opt/kubernetes/{bin,ssl,cfg}
##複製證書到存放點
[root@k8s_master k8s-cert]# cp -p *.pem /opt/kubernetes/ssl/
[root@k8s_master k8s-cert]# ls /opt/kubernetes/ssl/
admin-key.pem admin.pem ca-key.pem ca.pem kube-proxy-key.pem kube-proxy.pem server-key.pem server.pem
- 下載並解壓kubernetes-server二進制源碼包,
https://dl.k8s.io/v1.16.6/kubernetes-server-linux-amd64.tar.gz(自行解決翻牆問題)
[root@k8s_master bin]# tar zxvf kubernetes-server-linux-amd64.tar.gz
[root@k8s_master ~]# cd kubernetes/server/bin/
##複製關鍵命令道存放點
[root@k8s_master bin]# cp kube-apiserver kubectl kube-controller-manager kube-scheduler kube-proxy kubelet /opt/kubernetes/bin/
- 創建token文件
[root@k8s_master cfg]# cd /opt/kubernetes/cfg
##生成序列號
[root@k8s_master cfg]# export BOOTSTRAP_TOKEN=$(head -c 16 /dev/urandom | od -An -t x | tr -d ' ')
[root@k8s_master cfg]# echo $BOOTSTRAP_TOKEN
c345888c7d4ffb7eacc5fdd56bef72c1
##創建token文件
[root@k8s_master cfg]# cat > token.csv << EOF
> ${BOOTSTRAP_TOKEN},kubelet-bootstrap,10001,"system:kubelet-bootstrap"
> EOF
- 創建apiserver啓動腳本
[root@k8s_master cfg]# vi apiserver.sh
##添加以下內容
#!/bin/bash
MASTER_ADDRESS=$1
ETCD_SERVERS=$2
cat <<EOF >/opt/kubernetes/cfg/kube-apiserver
KUBE_APISERVER_OPTS="--logtostderr=true \\
--v=4 \\
--etcd-servers=${ETCD_SERVERS} \\
--bind-address=${MASTER_ADDRESS} \\
--secure-port=6443 \\
--advertise-address=${MASTER_ADDRESS} \\
--allow-privileged=true \\
--service-cluster-ip-range=10.0.0.0/24 \\
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \\
--authorization-mode=RBAC,Node \\
--kubelet-https=true \\
--enable-bootstrap-token-auth \\
--token-auth-file=/opt/kubernetes/cfg/token.csv \\
--service-node-port-range=30000-50000 \\
--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/etcd/ssl/ca.pem \\
--etcd-certfile=/opt/etcd/ssl/server.pem \\
--etcd-keyfile=/opt/etcd/ssl/server-key.pem"
EOF
cat <<EOF >/usr/lib/systemd/system/kube-apiserver.service
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-apiserver
ExecStart=/opt/kubernetes/bin/kube-apiserver \$KUBE_APISERVER_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable kube-apiserver
systemctl restart kube-apiserver
- 開啓apiserver服務
[root@k8s_master cfg]# bash apiserver.sh 192.168.5.10 https://192.168.5.10:2379,https://192.168.5.20:2379,https://192.168.5.30:2379
##檢查服務進程是否開啓
[root@k8s_master cfg]# ps aux | grep kube-apiserver
root 52113 19.7 8.3 397232 313124 ? Ssl 23:30 0:10 /opt/kubernetes/bin/kube-apiserver --logtostderr=true --v=4 --etcd-servers=https://192.168.5.10:2379,https://192.168.5.20:2379,https://192.168.5.30:2379
......省略
- 創建Scheruler服務啓動腳本
[root@k8s_master cfg]# vi scheduler.sh
##添加以下內容
#!/bin/bash
MASTER_ADDRESS=$1
cat <<EOF >/opt/kubernetes/cfg/kube-scheduler
KUBE_SCHEDULER_OPTS="--logtostderr=true \\
--v=4 \\
--master=${MASTER_ADDRESS}:8080 \\
--leader-elect"
EOF
cat <<EOF >/usr/lib/systemd/system/kube-scheduler.service
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-scheduler
ExecStart=/opt/kubernetes/bin/kube-scheduler \$KUBE_SCHEDULER_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable kube-scheduler
systemctl restart kube-scheduler
- 啓動Scheruler服務
[root@k8s_master cfg]# bash scheduler.sh 127.0.0.1
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-scheduler.service to /usr/lib/systemd/system/kube-scheduler.service.
- 創建kube-controller-manager啓動腳本
[root@k8s_master cfg]# vi controller-manager.sh
##添加以下內容
#!/bin/bash
MASTER_ADDRESS=$1
cat <<EOF >/opt/kubernetes/cfg/kube-controller-manager
KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=true \\
--v=4 \\
--master=${MASTER_ADDRESS}:8080 \\
--leader-elect=true \\
--address=127.0.0.1 \\
--service-cluster-ip-range=10.0.0.0/24 \\
--cluster-name=kubernetes \\
--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
cat <<EOF >/usr/lib/systemd/system/kube-controller-manager.service
[Unit]
Description=Kubernetes Controller Manager
Documentation=https://github.com/kubernetes/kubernetes
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-controller-manager
ExecStart=/opt/kubernetes/bin/kube-controller-manager \$KUBE_CONTROLLER_MANAGER_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable kube-controller-manager
systemctl restart kube-controller-manager
- 啓動kube-controller-manager服務
[root@k8s_master cfg]# bash controller-manager.sh 127.0.0.1
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-controller-manager.service to /usr/lib/systemd/system/kube-controller-manager.service.
- 查看master節點狀態
[root@k8s_master cfg]# /opt/kubernetes/bin/kubectl get cs
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
etcd-1 Healthy {"health":"true"}
etcd-0 Healthy {"health":"true"}
etcd-2 Healthy {"health":"true"}
##將命令寫入系統變量,方便使用
[root@k8s_master cfg]# echo 'PATH=/opt/kubernetes/bin/:$PATH' >> /etc/profile
[root@k8s_master cfg]# source /etc/profile
八、node節點部署
- 在master節點上操作
- 發送kubelet、kube-proxy命令到node節點上
[root@k8s_master bin]# cd /opt/kubernetes/bin/
[root@k8s_master bin]# scp kubelet kube-proxy root@192.168.5.20:/opt/kubernetes/bin/
[root@k8s_master bin]# scp kubelet kube-proxy root@192.168.5.30:/opt/kubernetes/bin/
- 配置kubeconfig文件,用於master和node互聯
[root@k8s_master ~]# mkdir /root/kubeconfig
[root@k8s_master ~]# vi /root/kubeconfig/kubeconfig.sh
###添加以下內容
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
# 設置客戶端認證參數
kubectl config set-credentials kubelet-bootstrap \
--token=c345888c7d4ffb7eacc5fdd56bef72c1 \
--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
- 執行kubeconfig文件,生成配置文件
[root@k8s_master kubeconfig]# bash kubeconfig 192.168.5.10 /root/k8s-cert
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".
[root@k8s_master kubeconfig]# ls
bootstrap.kubeconfig kubeconfig kube-proxy.kubeconfig
- 拷貝配置文件到node1節點
[root@k8s_master kubeconfig]# scp kube-proxy.kubeconfig bootstrap.kubeconfig root@192.168.5.20:/opt/kubernetes/cfg/
- 創建bootstrap角色賦予權限用於連接apiserver請求籤名
[root@k8s_master kubeconfig]# kubectl create clusterrolebinding kubelet-bootstrap \
> --clusterrole=system:node-bootstrapper \
> --user=kubelet-bootstrap
node1節點配置
- 編寫kubelet啓動腳本
[root@k8s_node1 cfg]# cd /opt/kubernetes/cfg/
[root@k8s_node1 cfg]# vi kubelet.sh
##添加以下內容
#!/bin/bash
NODE_ADDRESS=$1
DNS_SERVER_IP=${2:-"10.0.0.2"}
cat <<EOF >/opt/kubernetes/cfg/kubelet
KUBELET_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"
EOF
cat <<EOF >/opt/kubernetes/cfg/kubelet.config
kind: KubeletConfiguration
apiVersion: kubelet.config.k8s.io/v1beta1
address: ${NODE_ADDRESS}
port: 10250
readOnlyPort: 10255
cgroupDriver: cgroupfs
clusterDNS:
- ${DNS_SERVER_IP}
clusterDomain: cluster.local.
failSwapOn: false
authentication:
anonymous:
enabled: true
EOF
cat <<EOF >/usr/lib/systemd/system/kubelet.service
[Unit]
Description=Kubernetes Kubelet
After=docker.service
Requires=docker.service
[Service]
EnvironmentFile=/opt/kubernetes/cfg/kubelet
ExecStart=/opt/kubernetes/bin/kubelet \$KUBELET_OPTS
Restart=on-failure
KillMode=process
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable kubelet
systemctl restart kubelet
- 啓動kubelet服務
[root@k8s_node1 cfg]# bash kubelet.sh 192.168.5.20
Created symlink from /etc/systemd/system/multi-user.target.wants/kubelet.service to /usr/lib/systemd/system/kubelet.service.
[root@k8s_node1 cfg]# netstat -natp | grep kubelet
tcp 0 0 192.168.5.20:60028 192.168.5.10:6443 ESTABLISHED 61552/kubelet
- 返回master節點,給node的kubelet頒發證書
##查看請求
[root@k8s_master kubeconfig]# kubectl get csr
NAME AGE REQUESTOR CONDITION
node-csr-fW-g9h9PRMbM3HfS_1CpUsNktiK0zNxRBI-qcmB5sLk 4m12s kubelet-bootstrap Pending
###同意請求,頒發證書
[root@k8s_master kubeconfig]# kubectl certificate approve node-csr-fW-g9h9PRMbM3HfS_1CpUsNktiK0zNxRBI-qcmB5sLk
##再次查看請求,發現處於Approved狀態
[root@k8s_master kubeconfig]# kubectl get csr
NAME AGE REQUESTOR CONDITION
node-csr-fW-g9h9PRMbM3HfS_1CpUsNktiK0zNxRBI-qcmB5sLk 8m39s kubelet-bootstrap Approved,Issued
##此時node1節點已經加入到羣集中
[root@k8s_master kubeconfig]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
192.168.5.20 Ready <none> 119s v1.12.3
- 進入node1節點創建proxy代理腳本,並啓動
[root@k8s_node1 cfg]# vi /opt/kubernetes/cfg/proxy.sh
##添加以下內容
#!/bin/bash
NODE_ADDRESS=$1
cat <<EOF >/opt/kubernetes/cfg/kube-proxy
KUBE_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"
EOF
cat <<EOF >/usr/lib/systemd/system/kube-proxy.service
[Unit]
Description=Kubernetes Proxy
After=network.target
[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-proxy
ExecStart=/opt/kubernetes/bin/kube-proxy \$KUBE_PROXY_OPTS
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable kube-proxy
systemctl restart kube-proxy
####啓動服務
[root@k8s_node1 cfg]# bash proxy.sh 192.168.5.20
Created symlink from /etc/systemd/system/multi-user.target.wants/kube-proxy.service to /usr/lib/systemd/system/kube-proxy.service.
##檢查是否啓動
[root@k8s_node1 cfg]# netstat -natp | grep proxy
tcp 0 0 127.0.0.1:10249 0.0.0.0:* LISTEN 64440/kube-proxy
tcp 0 0 192.168.5.20:60888 192.168.5.10:6443 ESTABLISHED 64440/kube-proxy
tcp6 0 0 :::10256 :::* LISTEN 64440/kube-proxy
node2節點配置
- 在node1幾點上覆制配置文件到node2
[root@k8s_node1 cfg]# scp -r /opt/kubernetes/ root@192.168.5.30:/opt
##複製啓動文件到node2
[root@k8s_node1 cfg]# cd /usr/lib/systemd/system
[root@k8s_node1 system]# scp kube* root@192.168.5.30:/usr/lib/systemd/system/
- 在node2節點上,修改配置文件
##刪除複製過來的證書,node2會自行申請
[root@k8s_node1 system]# rm -rf /opt/kubernetes/ssl/*
##修改kubelet
[root@k8s_node1sy stem]# vi /opt/kubernetes/cfg/kubelet
--hostname-override=192.168.5.30 \ ##修改ip爲node2地址,192.168.5.30
##修改kubelet.config 文件
[root@k8s_node1 kubernetes]# vi /opt/kubernetes/cfg/kubelet.config
address: 192.168.5.30 ##修改ip爲node2地址,192.168.5.30
##修改kube-proxy
[root@k8s_node2 system]# vi /opt/kubernetes/cfg/kube-proxy
--hostname-override=192.168.5.30 \ ##修改ip爲node2地址,192.168.5.30
- 開啓node2的kubelet和proxy服務
[root@k8s_node2 system]# systemctl start kubelet
[root@k8s_node2 system]# systemctl enable kubelet
[root@k8s_node2 system]# systemctl start kube-proxy.service
[root@k8s_node2 system]# systemctl enable kube-proxy.service
九、驗證羣集信息
- 進入master節點,查看收到的請求,並給kubelet頒發證書
[root@k8s_master kubeconfig]# kubectl get csr
NAME AGE REQUESTOR CONDITION
node-csr-Tm1PmuZZFV0wyMrs3RV3SCpr080CRK9d9LnRHGg2jGE 4m12s kubelet-bootstrap Pending
node-csr-fW-g9h9PRMbM3HfS_1CpUsNktiK0zNxRBI-qcmB5sLk 44m kubelet-bootstrap Approved,Issued
##同意請求
[root@k8s_master kubeconfig]# kubectl certificate approve node-csr-Tm1PmuZZFV0wyMrs3RV3SCpr080CRK9d9LnRHGg2jGE
- 查看羣集節點信息
[root@k8s_master kubeconfig]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
192.168.5.20 Ready <none> 39m v1.12.3
192.168.5.30 Ready <none> 63s v1.12.3