二進位制部署高可用k8s叢集

阿新 • • 發佈：2022-12-09

一、k8s高可用架構解析

etcd是鍵值資料庫用來儲存叢集資訊

apiserver是叢集的整個控制中心，所有的流量都會經過他

ControllerManager控制器，監控整個叢集的狀態

Scheduler排程器

如果master也要部署pod的話需要安裝kubelet跟kube-proxy元件

圖中被勾的元件都是通過訪問LB提供的vip去訪問apiserver的，只有apiserver能訪問etcd資料庫。

LB會進行選主，會把vip掛載到其中一臺master節點的網絡卡上面

面試點：

叢集master可以是偶數個，etcd必須是奇數個，因為使用的是raft演算法。

參考資料：raft演算法

，k8s架構。

1.1 安裝說明

二進位制安裝方式比kubeadm的穩定性更高。

二進位制安裝證書有效期可以設定為100年，kubeadm證書有效期為一年。

二進位制重啟恢復速度比kubeadm快。

升級方式不一樣，二進位制替換包就行，所以二進位制維護比kubeadm簡單。

注意：關掉電腦時，沒關虛擬機器，那麼kubeadm就可能啟動不了了

基本環境配置跟核心升級都跟kubeadm一樣，這裡就不多寫了，可參考：核心升級

1.2 下載軟體

二進位制檔案是可以直接執行的，所以下載檔案放到相應目錄即安裝完成。

需要注意的是先確定裝什麼樣的版本，alpha是內測版本，不建議使用。

目前最新版本v1.25，我這裡安裝的是v1.23.13版本，官方文件：

https://kubernetes.io/zh-cn/

Master01下載kubernetes安裝包，這裡選擇v1.23

下載連結：https://github.com/kubernetes/kubernetes/tree/master/CHANGELOG

選擇amd64架構的下載

裡面會有其他元件版本介紹，可以看到k8s已經支援etcd 3.5.1的版本

軟體包下載：百度網盤

以下操作在master01執行

#下載軟體包
wget https://dl.k8s.io/v1.23.13/kubernetes-server-linux-amd64.tar.gz

#解壓kubernetes安裝檔案
tar -xf kubernetes-server-linux-amd64.tar.gz  --strip-components=3 -C /usr/local/bin kubernetes/server/bin/kube{let,ctl,-apiserver,-controller-manager,-scheduler,-proxy}

#解壓etcd安裝檔案
tar -zxvf etcd-v3.5.1-linux-amd64.tar.gz --strip-components=1 -C /usr/local/bin etcd-v3.5.1-linux-amd64/etcd{,ctl}

#版本檢視
[root@k8s-master01 ~]# kubelet --version
Kubernetes v1.23.12
[root@k8s-master01 ~]# etcdctl version
etcdctl version: 3.5.1
API version: 3.5

#將元件傳送到其他節點
MasterNodes='k8s-master02 k8s-master03'
WorkNodes='k8s-node01 k8s-node02'
for NODE in $MasterNodes; do echo $NODE; scp /usr/local/bin/kube{let,ctl,-apiserver,-controller-manager,-scheduler,-proxy} $NODE:/usr/local/bin/; scp /usr/local/bin/etcd* $NODE:/usr/local/bin/; done
for NODE in $WorkNodes; do scp /usr/local/bin/kube{let,-proxy} $NODE:/usr/local/bin/ ; done

#所有節點建立/opt/cni/bin目錄
mkdir -p /opt/cni/bin

#Master01節點切換到1.23.x分支
cd /root/k8s-ha-install && git checkout manual-installation-v1.23.x

二、生成證書

證書之間的生成關係是：證書籤名請求檔案CSR→CA根證書檔案→其他證書檔案

證書在master01節點上生成，然後再把證書檔案傳送到各個節點上。

Master01下載生成證書工具

wget "https://pkg.cfssl.org/R1.2/cfssl_linux-amd64" -O /usr/local/bin/cfssl
wget "https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64" -O /usr/local/bin/cfssljson

#如果是上傳到伺服器上的執行
mv cfssl_linux-amd64 /usr/local/bin/cfssl
mv cfssljson_linux-amd64 /usr/local/bin/cfssljson
chmod +x /usr/local/bin/cfssl /usr/local/bin/cfssljson

2.1 etcd證書

#所有Master節點建立etcd證書目錄
mkdir /etc/etcd/ssl -p

#所有節點建立kubernetes相關目錄，這裡保持跟kubeadm同樣的證書目錄，方便找
mkdir -p /etc/kubernetes/pki

Master01節點生成etcd證書

生成證書的CSR檔案：證書籤名請求檔案，配置了一些域名、公司、單位

cd /root/k8s-ha-install/pki

#生成etcd CA證書和CA證書的key，這裡的etcd-ca-csr.json裡面設定了證書過期時間
#他們之間的聯絡是，通過證書籤名請求檔案生成根證書，再通過根證書生成其他證書
cfssl gencert -initca etcd-ca-csr.json | cfssljson -bare /etc/etcd/ssl/etcd-ca

#證書的生成會繫結ip地址跟域名，這裡繫結的是etcd的主機名跟ip地址，因為實驗環境中etcd是裝在master節點上的，所以用的是master的主機名跟地址，也可以多寫幾個預留地址
cfssl gencert \
   -ca=/etc/etcd/ssl/etcd-ca.pem \
   -ca-key=/etc/etcd/ssl/etcd-ca-key.pem \
   -config=ca-config.json \
   -hostname=127.0.0.1,k8s-master01,k8s-master02,k8smaster03,10.103.236.201,10.103.236.202,10.103.236.203 \
   -profile=kubernetes \
   etcd-csr.json | cfssljson -bare /etc/etcd/ssl/etcd
   
#該目錄下會生成6個證書檔案  
ls /etc/etcd/ssl/  
 
#將證書複製到其他節點
MasterNodes='k8s-master02 k8s-master03'

for NODE in $MasterNodes; do
     ssh $NODE "mkdir -p /etc/etcd/ssl"
     for FILE in etcd-ca-key.pem  etcd-ca.pem  etcd-key.pem  etcd.pem; do
       scp /etc/etcd/ssl/${FILE} $NODE:/etc/etcd/ssl/${FILE}
     done
 done

2.2 apiserver證書

　Master01生成kubernetes證書

[root@k8s-master01 pki]# cd /root/k8s-ha-install/pki

#生成根證書，會有3個檔案
cfssl gencert -initca ca-csr.json | cfssljson -bare /etc/kubernetes/pki/ca
ls  /etc/kubernetes/pki/

# 192.168.0.是k8s service的網段的第一個IP地址，注意掩碼劃分。
# 如果不是高可用叢集，10.103.236.236為Master01的IP
cfssl gencert \
-ca=/etc/kubernetes/pki/ca.pem \
-ca-key=/etc/kubernetes/pki/ca-key.pem \
-config=ca-config.json \
-hostname=192.168.0.1,10.103.236.236,127.0.0.1,kubernetes,kubernetes.default,kubernetes.default.svc,kubernetes.default.svc.cluster,kubernetes.default.svc.cluster.local,10.103.236.201,10.103.236.202,10.103.236.203 \
-profile=kubernetes \
apiserver-csr.json | cfssljson -bare /etc/kubernetes/pki/apiserver

#可以看到有3個以apiserver開頭的檔案
ls /etc/kubernetes/pki/

2.3 生成聚合證書

apiserver的證書劃分的許可權很大，聚合證書劃分的許可權較小，用於其他第三方元件授權使用，如Metrics-server元件，避免安全問題。

cfssl gencert \
-initca front-proxy-ca-csr.json | cfssljson -bare /etc/kubernetes/pki/front-proxy-ca 

cfssl gencert \
-ca=/etc/kubernetes/pki/front-proxy-ca.pem \
-ca-key=/etc/kubernetes/pki/front-proxy-ca-key.pem \
-config=ca-config.json \
-profile=kubernetes \
front-proxy-client-csr.json | cfssljson -bare /etc/kubernetes/pki/front-proxy-client
#返回結果，可以忽略WARNING警告

2.4 controller-manage證書

生成controller-manage的證書，controller需要跟apiserver通訊，所以需要證書。

如下步驟會將證書相關資訊跟apiserver的地址寫入controller-manager.kubeconfig檔案中，controller-manage會帶著這個檔案去跟apiserver進行通訊。

cfssl gencert \
   -ca=/etc/kubernetes/pki/ca.pem \
   -ca-key=/etc/kubernetes/pki/ca-key.pem \
   -config=ca-config.json \
   -profile=kubernetes \
   manager-csr.json | cfssljson -bare /etc/kubernetes/pki/controller-manager

# 注意，如果不是高可用叢集，10.103.236.236:8443改為master01的地址，8443改為apiserver的埠，預設是6443
# set-cluster：設定一個叢集項，叢集名字為kubernetes，因為K8s可以管理多個叢集，多個叢集使用名字進行區分
#--embed-certs=true 會將ca.pem證書內容匯入到controller-manager.kubeconfig檔案中，如果不為true，則匯入ca.pem證書路徑，推薦匯入內容
kubectl config set-cluster kubernetes \
     --certificate-authority=/etc/kubernetes/pki/ca.pem \
     --embed-certs=true \
     --server=https://10.103.236.236:8443 \
     --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig

#上述的操作是將叢集項資訊匯入了controller-manager.kubeconfig檔案中
# 設定上下文，相當於配置了一個系統使用者kube-controller-manager	
kubectl config set-context system:kube-controller-manager@kubernetes \
    --cluster=kubernetes \
    --user=system:kube-controller-manager \
    --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig

#設定一個使用者項，將證書匯入controller-manager.kubeconfig
kubectl config set-credentials system:kube-controller-manager \
     --client-certificate=/etc/kubernetes/pki/controller-manager.pem \
     --client-key=/etc/kubernetes/pki/controller-manager-key.pem \
     --embed-certs=true \
     --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig


# 設定預設叢集環境，kubeconfig檔案中可以配置多個叢集，這裡指定kubernetes為預設叢集環境
kubectl config use-context system:kube-controller-manager@kubernetes \
     --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig

2.5 scheduler證書

生成scheduler證書，用於跟apiserver進行通訊

cfssl gencert \
   -ca=/etc/kubernetes/pki/ca.pem \
   -ca-key=/etc/kubernetes/pki/ca-key.pem \
   -config=ca-config.json \
   -profile=kubernetes \
   scheduler-csr.json | cfssljson -bare /etc/kubernetes/pki/scheduler

# 注意，如果不是高可用叢集，10.103.236.236:8443改為master01的地址，8443改為apiserver的埠，預設是6443
#設定叢集項
kubectl config set-cluster kubernetes \
     --certificate-authority=/etc/kubernetes/pki/ca.pem \
     --embed-certs=true \
     --server=https://10.103.236.236:8443 \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

#設定上下文
kubectl config set-credentials system:kube-scheduler \
     --client-certificate=/etc/kubernetes/pki/scheduler.pem \
     --client-key=/etc/kubernetes/pki/scheduler-key.pem \
     --embed-certs=true \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

#設定使用者項
kubectl config set-context system:kube-scheduler@kubernetes \
     --cluster=kubernetes \
     --user=system:kube-scheduler \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

# 設定預設叢集環境
kubectl config use-context system:kube-scheduler@kubernetes \
     --kubeconfig=/etc/kubernetes/scheduler.kubeconfig

2.6 管理員證書證書

生成管理員證書admin.kubeconfig，相當於kubeadm的admin.conf檔案，用於kubectl訪問叢集

cfssl gencert \
   -ca=/etc/kubernetes/pki/ca.pem \
   -ca-key=/etc/kubernetes/pki/ca-key.pem \
   -config=ca-config.json \
   -profile=kubernetes \
   admin-csr.json | cfssljson -bare /etc/kubernetes/pki/admin

# 注意，如果不是高可用叢集，10.103.236.236:8443改為master01的地址，8443改為apiserver的埠，預設是6443
#設定叢集項
kubectl config set-cluster kubernetes \
--certificate-authority=/etc/kubernetes/pki/ca.pem   \  
--embed-certs=true \
--server=https://10.103.236.236:8443 \
--kubeconfig=/etc/kubernetes/admin.kubeconfig

#設定上下文
kubectl config set-credentials kubernetes-admin \
--client-certificate=/etc/kubernetes/pki/admin.pem \     
--client-key=/etc/kubernetes/pki/admin-key.pem \
--embed-certs=true \
--kubeconfig=/etc/kubernetes/admin.kubeconfig

#設定使用者項
kubectl config set-context kubernetes-admin@kubernetes \
--cluster=kubernetes \
--user=kubernetes-admin \
--kubeconfig=/etc/kubernetes/admin.kubeconfig

#設定預設叢集環境
kubectl config use-context kubernetes-admin@kubernetes \
--kubeconfig=/etc/kubernetes/admin.kubeconfig

ls /etc/kubernetes/admin.kubeconfig

#不配置環境變數的情況下，指定該使用者證書就對該叢集執行命令了
kubectl --kubeconfig /etc/kubernetes/admin.kubeconfig get node

生成金鑰對，用建立ServiceAccount Key的token。

#生成私鑰
openssl genrsa -out /etc/kubernetes/pki/sa.key 2048

#生成公鑰
openssl rsa -in /etc/kubernetes/pki/sa.key -pubout -out /etc/kubernetes/pki/sa.pub

建立ServiceAccount（服務賬戶）時會生成對應的secret，這個secret裡面會有一個token，這個token就是controller-manage基於這兩個證書來生成的。

傳送證書至其他節點

for NODE in k8s-master02 k8s-master03; do
for FILE in $(ls /etc/kubernetes/pki | grep -v etcd); do
scp /etc/kubernetes/pki/${FILE} $NODE:/etc/kubernetes/pki/${FILE};
done;
for FILE in admin.kubeconfig controller-manager.kubeconfig scheduler.kubeconfig; do
scp /etc/kubernetes/${FILE} $NODE:/etc/kubernetes/${FILE};
done;
done

檢視證書檔案

[root@k8s-master01 pki]# ls /etc/kubernetes/pki/
admin.csr      apiserver.csr      ca.csr      controller-manager.csr      front-proxy-ca.csr      front-proxy-client.csr      sa.key         scheduler-key.pem
admin-key.pem  apiserver-key.pem  ca-key.pem  controller-manager-key.pem  front-proxy-ca-key.pem  front-proxy-client-key.pem  sa.pub         scheduler.pem
admin.pem      apiserver.pem      ca.pem      controller-manager.pem      front-proxy-ca.pem      front-proxy-client.pem      scheduler.csr
[root@k8s-master01 pki]# ls /etc/kubernetes/pki/ |wc -l
23  #一共有23個證書

三、高可用配置

高可用配置（注意：如果不是高可用叢集，haproxy和keepalived無需安裝）

如果在雲上安裝也無需執行此章節的步驟，可以直接使用雲上的lb，比如阿里雲slb，騰訊雲elb等

公有云要用公有云自帶的負載均衡，比如阿里雲的SLB，騰訊雲的ELB，用來替代haproxy和keepalived，因為公有云大部分都是不支援keepalived的，另外如果用阿里雲的話，kubectl控制端不能放在master節點，推薦使用騰訊雲，因為阿里雲的slb有迴環的問題，也就是slb代理的伺服器不能反向訪問SLB，但是騰訊雲修復了這個問題。

Slb -> haproxy -> apiserver

3.1 配置haproxy

所有Master節點安裝keepalived和haproxy

yum install keepalived haproxy -y

所有Master配置HAProxy，配置都一樣，為了跟kubeadm區分，這裡把埠號改為了8443，kubeadm使用的是16443

vim /etc/haproxy/haproxy.cfg 
global
  maxconn  2000
  ulimit-n  16384
  log  127.0.0.1 local0 err
  stats timeout 30s

defaults
  log global
  mode  http
  option  httplog
  timeout connect 5000
  timeout client  50000
  timeout server  50000
  timeout http-request 15s
  timeout http-keep-alive 15s

frontend k8s-master
  bind 0.0.0.0:8443
  bind 127.0.0.1:8443
  mode tcp
  option tcplog
  tcp-request inspect-delay 5s
  default_backend k8s-master

backend k8s-master
  mode tcp
  option tcplog
  option tcp-check
  balance roundrobin
  default-server inter 10s downinter 5s rise 2 fall 2 slowstart 60s maxconn 250 maxqueue 256 weight 100
  server k8s-master01    10.103.236.201:6443  check
  server k8s-master02    10.103.236.202:6443  check
  server k8s-master03    10.103.236.203:6443  check

3.2 配置keepalived

Master01 keepalived的配置

所有Master節點配置KeepAlived，配置不一樣，注意區分每個節點的IP和網絡卡（interface引數）

[root@k8s-master01 pki]# vim /etc/keepalived/keepalived.conf 
! Configuration File for keepalived
global_defs {
    router_id LVS_DEVEL
}
vrrp_script chk_apiserver {
    script "/etc/keepalived/check_apiserver.sh"
    interval 5 
    weight -5
    fall 2
    rise 1
}
vrrp_instance VI_1 {
    state MASTER
    interface ens33
    mcast_src_ip 10.103.236.201
    virtual_router_id 51
    priority 101
    nopreempt
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass K8SHA_KA_AUTH
    }
    virtual_ipaddress {
        10.103.236.236
    }
    track_script {
      chk_apiserver 
} }

Master02 keepalived的配置

vim /etc/keepalived/keepalived.conf 
! Configuration File for keepalived
global_defs {
    router_id LVS_DEVEL
}
vrrp_script chk_apiserver {
    script "/etc/keepalived/check_apiserver.sh"
    interval 5 
    weight -5
    fall 2
    rise 1
}
vrrp_instance VI_1 {
    state BACKUP
    interface ens33
    mcast_src_ip 10.103.236.202
    virtual_router_id 51
    priority 100
    nopreempt
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass K8SHA_KA_AUTH
    }
    virtual_ipaddress {
        10.103.236.236
    }
    track_script {
      chk_apiserver 
} }

Master03 keepalived的配置

vim /etc/keepalived/keepalived.conf 
! Configuration File for keepalived
global_defs {
    router_id LVS_DEVEL
}
vrrp_script chk_apiserver {
    script "/etc/keepalived/check_apiserver.sh"
    interval 5
    weight -5
    fall 2  
    rise 1
}
vrrp_instance VI_1 {
    state BACKUP
    interface ens33
    mcast_src_ip 10.103.236.203
    virtual_router_id 51
    priority 100
    nopreempt
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass K8SHA_KA_AUTH
    }
    virtual_ipaddress {
        10.103.236.236
    }
    track_script {
      chk_apiserver 
} }

3.3 健康檢查配置

所有master節點

[root@k8s-master01 keepalived]# vim /etc/keepalived/check_apiserver.sh 

#!/bin/bash

err=0
for k in $(seq 1 3)
do
    check_code=$(pgrep haproxy)
    if [[ $check_code == "" ]]; then
        err=$(expr $err + 1)
        sleep 1
        continue
    else
        err=0
        break
    fi
done

if [[ $err != "0" ]]; then
    echo "systemctl stop keepalived"
    /usr/bin/systemctl stop keepalived
    exit 1
else
    exit 0
fi

新增許可權

chmod +x /etc/keepalived/check_apiserver.sh

所有master節點啟動haproxy和keepalived

systemctl daemon-reload
systemctl enable --now haproxy
systemctl enable --now keepalived

驗證

#啟動之後看下埠起來沒，埠是8443
netstat -lntp | grep 8443

#看日誌
tail -f /var/log/message

#看下10.103.236.236繫結在哪臺master節點上了，通過IP a看

ping  10.103.236.236

重要：如果安裝了keepalived和haproxy，需要測試keepalived是否是正常的

telnet 10.103.236.236 8443

如果ping不通且telnet沒有出現 ]，則認為VIP不可以，不可在繼續往下執行，需要排查keepalived的問題，比如防火牆和selinux，haproxy和keepalived的狀態，監聽埠等

所有節點檢視防火牆狀態必須為disable和inactive：systemctl status firewalld

所有節點檢視selinux狀態，必須為disable：getenforce

master節點檢視haproxy和keepalived狀態：systemctl status keepalived haproxy

master節點檢視監聽埠：netstat -lntp

四、系統元件配置

4.1 etcd

etcd配置大致相同，注意修改每個Master節點的etcd配置的主機名和IP地址

即便是單節點的master，etcd也需要三臺起，因為etcd是叢集的資料庫，掛掉資料就會丟失

master01配置如下

vim /etc/etcd/etcd.config.yml
name: 'k8s-master01'
data-dir: /var/lib/etcd
wal-dir: /var/lib/etcd/wal
snapshot-count: 5000
heartbeat-interval: 100
election-timeout: 1000
quota-backend-bytes: 0
listen-peer-urls: 'https://10.103.236.201:2380'
listen-client-urls: 'https://10.103.236.201:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.103.236.201:2380'
advertise-client-urls: 'https://10.103.236.201:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'k8s-master01=https://10.103.236.201:2380,k8s-master02=https://10.103.236.202:2380,k8s-master03=https://10.103.236.203:2380'
initial-cluster-token: 'etcd-k8s-cluster'
initial-cluster-state: 'new'
strict-reconfig-check: false
enable-v2: true
enable-pprof: true
proxy: 'off'
proxy-failure-wait: 5000
proxy-refresh-interval: 30000
proxy-dial-timeout: 1000
proxy-write-timeout: 5000
proxy-read-timeout: 0
client-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
peer-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  peer-client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false

需要注意第一行name: 'k8s-master01'，以及下面的Ip地址別寫錯了。

master02配置如下

vim /etc/etcd/etcd.config.yml
name: 'k8s-master02'
data-dir: /var/lib/etcd
wal-dir: /var/lib/etcd/wal
snapshot-count: 5000
heartbeat-interval: 100
election-timeout: 1000
quota-backend-bytes: 0
listen-peer-urls: 'https://10.103.236.202:2380'
listen-client-urls: 'https://10.103.236.202:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.103.236.202:2380'
advertise-client-urls: 'https://10.103.236.202:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'k8s-master01=https://10.103.236.201:2380,k8s-master02=https://10.103.236.202:2380,k8s-master03=https://10.103.236.203:2380'
initial-cluster-token: 'etcd-k8s-cluster'
initial-cluster-state: 'new'
strict-reconfig-check: false
enable-v2: true
enable-pprof: true
proxy: 'off'
proxy-failure-wait: 5000
proxy-refresh-interval: 30000
proxy-dial-timeout: 1000
proxy-write-timeout: 5000
proxy-read-timeout: 0
client-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
peer-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  peer-client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false

master03配置如下

vim /etc/etcd/etcd.config.yml
name: 'k8s-master03'
data-dir: /var/lib/etcd
wal-dir: /var/lib/etcd/wal
snapshot-count: 5000
heartbeat-interval: 100
election-timeout: 1000
quota-backend-bytes: 0
listen-peer-urls: 'https://10.103.236.203:2380'
listen-client-urls: 'https://10.103.236.203:2379,http://127.0.0.1:2379'
max-snapshots: 3
max-wals: 5
cors:
initial-advertise-peer-urls: 'https://10.103.236.203:2380'
advertise-client-urls: 'https://10.103.236.203:2379'
discovery:
discovery-fallback: 'proxy'
discovery-proxy:
discovery-srv:
initial-cluster: 'k8s-master01=https://10.103.236.201:2380,k8s-master02=https://10.103.236.202:2380,k8s-master03=https://10.103.236.203:2380'
initial-cluster-token: 'etcd-k8s-cluster'
initial-cluster-state: 'new'
strict-reconfig-check: false
enable-v2: true
enable-pprof: true
proxy: 'off'
proxy-failure-wait: 5000
proxy-refresh-interval: 30000
proxy-dial-timeout: 1000
proxy-write-timeout: 5000
proxy-read-timeout: 0
client-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
peer-transport-security:
  cert-file: '/etc/kubernetes/pki/etcd/etcd.pem'
  key-file: '/etc/kubernetes/pki/etcd/etcd-key.pem'
  peer-client-cert-auth: true
  trusted-ca-file: '/etc/kubernetes/pki/etcd/etcd-ca.pem'
  auto-tls: true
debug: false
log-package-levels:
log-outputs: [default]
force-new-cluster: false

建立Service

二進位制是以linux守護程序啟動的所以需要建立service檔案

所有Master節點建立etcd service並啟動

vim /usr/lib/systemd/system/etcd.service
[Unit]
Description=Etcd Service
Documentation=https://coreos.com/etcd/docs/latest/
After=network.target

[Service]
Type=notify
ExecStart=/usr/local/bin/etcd --config-file=/etc/etcd/etcd.config.yml
Restart=on-failure
RestartSec=10
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
Alias=etcd3.service

因為上述配置的證書檔案在/etc/kubernetes/pki/etcd/，而我們生成的目錄在/etc/etcd/ssl/，所以需要做一個軟連結

所有Master節點建立etcd的證書目錄

mkdir /etc/kubernetes/pki/etcd
ln -s /etc/etcd/ssl/* /etc/kubernetes/pki/etcd/
systemctl daemon-reload

#注意三個節點要一起啟動，不然可能會失敗
systemctl enable --now etcd

#檢視是否有無報錯
tail -f /var/log/messages #看到的都是info日誌那就是沒問題

檢視etcd狀態

$ export ETCDCTL_API=3
etcdctl --endpoints="10.103.236.203:2379,10.103.236.202:2379,10.103.236.201:2379" \
--cacert=/etc/kubernetes/pki/etcd/etcd-ca.pem \
--cert=/etc/kubernetes/pki/etcd/etcd.pem \
--key=/etc/kubernetes/pki/etcd/etcd-key.pem  endpoint status --write-out=table

注意LEADER，兩個false一個true表示一主兩從，主寫從讀，主掛了會自動選主

4.2 apiserver

所有master節點建立相關目錄

mkdir -p /etc/kubernetes/manifests/ /etc/systemd/system/kubelet.service.d /var/lib/kubelet /var/log/kubernetes

注意，如果不是高可用叢集，10.103.236.236改為master01的地址，本文件使用的k8s service網段為192.168.0.0/16，該網段不能和宿主機的網段、Pod網段的重複，請按需修改

Master01配置

[root@k8s-master01 pki]# vim /usr/lib/systemd/system/kube-apiserver.service 

[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
After=network.target

[Service]
ExecStart=/usr/local/bin/kube-apiserver \
      --v=2  \
      --logtostderr=true  \
      --allow-privileged=true  \
      --bind-address=0.0.0.0  \
      --secure-port=6443  \
      --insecure-port=0  \
      --advertise-address=10.103.236.201 \
      --service-cluster-ip-range=192.168.0.0/16  \
      --service-node-port-range=30000-32767  \
      --etcd-servers=https://10.103.236.201:2379,https://10.103.236.202:2379,https://10.103.236.203:2379 \
      --etcd-cafile=/etc/etcd/ssl/etcd-ca.pem  \
      --etcd-certfile=/etc/etcd/ssl/etcd.pem  \
      --etcd-keyfile=/etc/etcd/ssl/etcd-key.pem  \
      --client-ca-file=/etc/kubernetes/pki/ca.pem  \
      --tls-cert-file=/etc/kubernetes/pki/apiserver.pem  \
      --tls-private-key-file=/etc/kubernetes/pki/apiserver-key.pem  \
      --kubelet-client-certificate=/etc/kubernetes/pki/apiserver.pem  \
      --kubelet-client-key=/etc/kubernetes/pki/apiserver-key.pem  \
      --service-account-key-file=/etc/kubernetes/pki/sa.pub  \
      --service-account-signing-key-file=/etc/kubernetes/pki/sa.key  \
      --service-account-issuer=https://kubernetes.default.svc.cluster.local \
      --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname  \
      --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,ResourceQuota  \
      --authorization-mode=Node,RBAC  \
      --enable-bootstrap-token-auth=true  \
      --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.pem  \
      --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.pem  \
      --proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client-key.pem  \
      --requestheader-allowed-names=aggregator  \
      --requestheader-group-headers=X-Remote-Group  \
      --requestheader-extra-headers-prefix=X-Remote-Extra-  \
      --requestheader-username-headers=X-Remote-User
      # --token-auth-file=/etc/kubernetes/token.csv

Restart=on-failure
RestartSec=10s
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target

master02配置

注意本文件使用的k8s service網段為192.168.0.0/16，該網段不能和宿主機的網段、Pod網段的重複，請按需修改

[root@k8s-master01 pki]# vim  /usr/lib/systemd/system/kube-apiserver.service 

[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
After=network.target

[Service]
ExecStart=/usr/local/bin/kube-apiserver \
      --v=2  \
      --logtostderr=true  \
      --allow-privileged=true  \
      --bind-address=0.0.0.0  \
      --secure-port=6443  \
      --insecure-port=0  \
      --advertise-address=10.103.236.202 \
      --service-cluster-ip-range=192.168.0.0/16  \
      --service-node-port-range=30000-32767  \
      --etcd-servers=https://10.103.236.201:2379,https://10.103.236.202:2379,https://10.103.236.203:2379 \
      --etcd-cafile=/etc/etcd/ssl/etcd-ca.pem  \
      --etcd-certfile=/etc/etcd/ssl/etcd.pem  \
      --etcd-keyfile=/etc/etcd/ssl/etcd-key.pem  \
      --client-ca-file=/etc/kubernetes/pki/ca.pem  \
      --tls-cert-file=/etc/kubernetes/pki/apiserver.pem  \
      --tls-private-key-file=/etc/kubernetes/pki/apiserver-key.pem  \
      --kubelet-client-certificate=/etc/kubernetes/pki/apiserver.pem  \
      --kubelet-client-key=/etc/kubernetes/pki/apiserver-key.pem  \
      --service-account-key-file=/etc/kubernetes/pki/sa.pub  \
      --service-account-signing-key-file=/etc/kubernetes/pki/sa.key  \
      --service-account-issuer=https://kubernetes.default.svc.cluster.local \
      --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname  \
      --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,ResourceQuota  \
      --authorization-mode=Node,RBAC  \
      --enable-bootstrap-token-auth=true  \
      --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.pem  \
      --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.pem  \
      --proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client-key.pem  \
      --requestheader-allowed-names=aggregator  \
      --requestheader-group-headers=X-Remote-Group  \
      --requestheader-extra-headers-prefix=X-Remote-Extra-  \
      --requestheader-username-headers=X-Remote-User
      # --token-auth-file=/etc/kubernetes/token.csv

Restart=on-failure
RestartSec=10s
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target

master03配置

注意本文件使用的k8s service網段為192.168.0.0/16，該網段不能和宿主機的網段、Pod網段的重複，請按需修改

[root@k8s-master01 pki]# vim  /usr/lib/systemd/system/kube-apiserver.service 

[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes
After=network.target

[Service]
ExecStart=/usr/local/bin/kube-apiserver \
      --v=2  \
      --logtostderr=true  \
      --allow-privileged=true  \
      --bind-address=0.0.0.0  \
      --secure-port=6443  \
      --insecure-port=0  \
      --advertise-address=10.103.236.203 \
      --service-cluster-ip-range=192.168.0.0/16  \
      --service-node-port-range=30000-32767  \
      --etcd-servers=https://10.103.236.201:2379,https://10.103.236.202:2379,https://10.103.236.203:2379 \
      --etcd-cafile=/etc/etcd/ssl/etcd-ca.pem  \
      --etcd-certfile=/etc/etcd/ssl/etcd.pem  \
      --etcd-keyfile=/etc/etcd/ssl/etcd-key.pem  \
      --client-ca-file=/etc/kubernetes/pki/ca.pem  \
      --tls-cert-file=/etc/kubernetes/pki/apiserver.pem  \
      --tls-private-key-file=/etc/kubernetes/pki/apiserver-key.pem  \
      --kubelet-client-certificate=/etc/kubernetes/pki/apiserver.pem  \
      --kubelet-client-key=/etc/kubernetes/pki/apiserver-key.pem  \
      --service-account-key-file=/etc/kubernetes/pki/sa.pub  \
      --service-account-signing-key-file=/etc/kubernetes/pki/sa.key  \
      --service-account-issuer=https://kubernetes.default.svc.cluster.local \
      --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname  \
      --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,ResourceQuota  \
      --authorization-mode=Node,RBAC  \
      --enable-bootstrap-token-auth=true  \
      --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.pem  \
      --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.pem  \
      --proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client-key.pem  \
      --requestheader-allowed-names=aggregator  \
      --requestheader-group-headers=X-Remote-Group  \
      --requestheader-extra-headers-prefix=X-Remote-Extra-  \
      --requestheader-username-headers=X-Remote-User
      # --token-auth-file=/etc/kubernetes/token.csv

Restart=on-failure
RestartSec=10s
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target

啟動apiserver

#所有Master節點開啟kube-apiserver
systemctl daemon-reload && systemctl enable --now kube-apiserver
systemctl status kube-apiserver
 
 # 沒有瘋狂的輸出日誌，那麼安裝就沒問題
 tail -f /var/log/messages

出現如下表示啟動成功

4.3 ControllerManager

所有Master節點配置kube-controller-manager service（所有master節點配置一樣）

注意本文件使用的k8s Pod網段為172.16.0.0/12，該網段不能和宿主機的網段、k8s Service網段的重複，請按需修改

[root@k8s-master01 pki]# vim /usr/lib/systemd/system/kube-controller-manager.service
[Unit]
Description=Kubernetes Controller Manager
Documentation=https://github.com/kubernetes/kubernetes
After=network.target

[Service]
ExecStart=/usr/local/bin/kube-controller-manager \
      --v=2 \
      --logtostderr=true \
      --address=127.0.0.1 \
      --root-ca-file=/etc/kubernetes/pki/ca.pem \
      --cluster-signing-cert-file=/etc/kubernetes/pki/ca.pem \
      --cluster-signing-key-file=/etc/kubernetes/pki/ca-key.pem \
      --service-account-private-key-file=/etc/kubernetes/pki/sa.key \
      --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig \
      --leader-elect=true \
      --use-service-account-credentials=true \
      --node-monitor-grace-period=40s \
      --node-monitor-period=5s \
      --pod-eviction-timeout=2m0s \
      --controllers=*,bootstrapsigner,tokencleaner \
      --allocate-node-cidrs=true \
      --cluster-cidr=172.16.0.0/12 \
      --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.pem \
      --node-cidr-mask-size=24
      
Restart=always
RestartSec=10s

[Install]
WantedBy=multi-user.target

所有Master節點啟動kube-controller-manager

systemctl daemon-reload
systemctl enable --now kube-controller-manager

I開頭的代表info日誌，是沒有問題的，如果是E開頭或者F開頭的需要注意一下

4.4 Scheduler

所有Master節點配置kube-scheduler service（所有master節點配置一樣）

[root@k8s-master01 pki]# vim /usr/lib/systemd/system/kube-scheduler.service 
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes
After=network.target

[Service]
ExecStart=/usr/local/bin/kube-scheduler \
      --v=2 \
      --logtostderr=true \
      --address=127.0.0.1 \
      --leader-elect=true \
      --kubeconfig=/etc/kubernetes/scheduler.kubeconfig 
Restart=always
RestartSec=10s

[Install]
WantedBy=multi-user.target

scheduler.kubeconfig 這個檔案就是和叢集通訊的檔案，裡面是生成的證書

啟動

systemctl daemon-reload
systemctl enable --now kube-scheduler

檢視日誌

tail -f /var/log/messages

五、TLS Bootstrapping配置

controller-manager和scheduler跟apiserver進行通訊靠的是xxx.kubeconfig檔案，每個節點都是一樣的kubeconfig配置檔案。

kubelet也需要跟apiserver進行通訊，但是kubelet跟主機是有繫結關係的，綁定了主機名跟IP地址，每個節點的資訊都是不一樣的，而且可能會有幾百個節點，所以需要使用bootstrapping自動申請證書。

kubelet啟動時指定bootstrap-kubelet.kubeconfig檔案就能自動去申請證書。

注意，如果不是高可用叢集，10.103.236.236:8443改為master01的地址，8443改為apiserver的埠，預設是6443

只需要在Master01建立bootstrap

cd /root/k8s-ha-install/bootstrap
#設定叢集項
kubectl config set-cluster kubernetes \
--certificate-authority=/etc/kubernetes/pki/ca.pem \
--embed-certs=true \   
--server=https://10.103.236.236:8443 \
--kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig

#設定上下文
kubectl config set-credentials tls-bootstrap-token-user \   
--token=c8ad9c.2e4d610cf3e7426e \
--kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig

#設定使用者項
kubectl config set-context tls-bootstrap-token-user@kubernetes \
--cluster=kubernetes \
--user=tls-bootstrap-token-user \
--kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig

#設定預設叢集環境
kubectl config use-context tls-bootstrap-token-user@kubernetes \   
--kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig

注意：如果修改了上下文中的token，則也要修改bootstrap.secret.yaml的name，token-id和token-secret

admin.kubeconfig跟之前kubeadm的admin.conf檔案一樣，如果使用kubectl訪問叢集，直接拷貝這個檔案到如下目錄就行

 mkdir -p /root/.kube ; cp /etc/kubernetes/admin.kubeconfig /root/.kube/config

可以正常查詢叢集狀態，才可以繼續往下，否則不行，需要排查k8s元件是否有故障

# kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE                         ERROR
scheduler            Healthy   ok                              
controller-manager   Healthy   ok                              
etcd-0               Healthy   {"health":"true","reason":""}   
etcd-2               Healthy   {"health":"true","reason":""}   
etcd-1               Healthy   {"health":"true","reason":""}

建立token

[root@k8s-master01 bootstrap]# kubectl create -f bootstrap.secret.yaml 
secret/bootstrap-token-c8ad9c created
clusterrolebinding.rbac.authorization.k8s.io/kubelet-bootstrap created
clusterrolebinding.rbac.authorization.k8s.io/node-autoapprove-bootstrap created
clusterrolebinding.rbac.authorization.k8s.io/node-autoapprove-certificate-rotation created
clusterrole.rbac.authorization.k8s.io/system:kube-apiserver-to-kubelet created
clusterrolebinding.rbac.authorization.k8s.io/system:kube-apiserver created

六、Node節點配置

6.1 kubelet

Master01節點複製證書至Node節點

cd /etc/kubernetes/

for NODE in k8s-master02 k8s-master03 k8s-node01 k8s-node02; do
     ssh $NODE mkdir -p /etc/kubernetes/pki
     for FILE in pki/ca.pem pki/ca-key.pem pki/front-proxy-ca.pem bootstrap-kubelet.kubeconfig; do
       scp /etc/kubernetes/$FILE $NODE:/etc/kubernetes/${FILE}
 done
 done

所有節點建立相關目錄,master節點也配置了kubelet

mkdir -p /var/lib/kubelet /var/log/kubernetes /etc/systemd/system/kubelet.service.d /etc/kubernetes/manifests/

　所有節點配置kubelet service

[root@k8s-master01 bootstrap]# vim  /usr/lib/systemd/system/kubelet.service

[Unit]
Description=Kubernetes Kubelet
Documentation=https://github.com/kubernetes/kubernetes

[Service]
ExecStart=/usr/local/bin/kubelet

Restart=always
StartLimitInterval=0
RestartSec=10

[Install]
WantedBy=multi-user.target

如果Runtime為Containerd，請使用如下Kubelet的配置：

如下配置單獨指定了/etc/kubernetes/kubelet-conf.yml配置檔案

所有節點配置kubelet service的配置檔案（也可以寫到kubelet.service）：

# Runtime為Containerd
# vim /etc/systemd/system/kubelet.service.d/10-kubelet.conf

[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig --kubeconfig=/etc/kubernetes/kubelet.kubeconfig"
Environment="KUBELET_SYSTEM_ARGS=--network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin --container-runtime=remote --runtime-request-timeout=15m --container-runtime-endpoint=unix:///run/containerd/containerd.sock --cgroup-driver=systemd"
Environment="KUBELET_CONFIG_ARGS=--config=/etc/kubernetes/kubelet-conf.yml"
Environment="KUBELET_EXTRA_ARGS=--node-labels=node.kubernetes.io/node='' "
ExecStart=
ExecStart=/usr/local/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_SYSTEM_ARGS $KUBELET_EXTRA_ARGS

如果Runtime為Docker，請使用如下Kubelet的配置：

# Runtime為Docker
# vim /etc/systemd/system/kubelet.service.d/10-kubelet.conf

[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.kubeconfig --kubeconfig=/etc/kubernetes/kubelet.kubeconfig"
Environment="KUBELET_SYSTEM_ARGS=--network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin"
Environment="KUBELET_CONFIG_ARGS=--config=/etc/kubernetes/kubelet-conf.yml --pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.5"
Environment="KUBELET_EXTRA_ARGS=--node-labels=node.kubernetes.io/node='' "
ExecStart=
ExecStart=/usr/local/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_SYSTEM_ARGS $KUBELET_EXTRA_ARGS

建立kubelet的配置檔案，如果以後要更改kubelet的配置就改這個檔案

注意：如果更改了k8s的service網段，需要更改kubelet-conf.yml 的clusterDNS:配置，改成k8s Service網段的第十個地址，比如192.168.0.10

[root@k8s-master01 bootstrap]# vim /etc/kubernetes/kubelet-conf.yml


apiVersion: kubelet.config.k8s.io/v1beta1
kind: KubeletConfiguration
address: 0.0.0.0
port: 10250
readOnlyPort: 10255
authentication:
  anonymous:
    enabled: false
  webhook:
    cacheTTL: 2m0s
    enabled: true
  x509:
    clientCAFile: /etc/kubernetes/pki/ca.pem
authorization:
  mode: Webhook
  webhook:
    cacheAuthorizedTTL: 5m0s
    cacheUnauthorizedTTL: 30s
cgroupDriver: systemd
cgroupsPerQOS: true
clusterDNS:
- 192.168.0.10
clusterDomain: cluster.local
containerLogMaxFiles: 5
containerLogMaxSize: 10Mi
contentType: application/vnd.kubernetes.protobuf
cpuCFSQuota: true
cpuManagerPolicy: none
cpuManagerReconcilePeriod: 10s
enableControllerAttachDetach: true
enableDebuggingHandlers: true
enforceNodeAllocatable:
- pods
eventBurst: 10
eventRecordQPS: 5
evictionHard:
  imagefs.available: 15%
  memory.available: 100Mi
  nodefs.available: 10%
  nodefs.inodesFree: 5%
evictionPressureTransitionPeriod: 5m0s
failSwapOn: true
fileCheckFrequency: 20s
hairpinMode: promiscuous-bridge
healthzBindAddress: 127.0.0.1
healthzPort: 10248
httpCheckFrequency: 20s
imageGCHighThresholdPercent: 85
imageGCLowThresholdPercent: 80
imageMinimumGCAge: 2m0s
iptablesDropBit: 15
iptablesMasqueradeBit: 14
kubeAPIBurst: 10
kubeAPIQPS: 5
makeIPTablesUtilChains: true
maxOpenFiles: 1000000
maxPods: 110
nodeStatusUpdateFrequency: 10s
oomScoreAdj: -999
podPidsLimit: -1
registryBurst: 10
registryPullQPS: 5
resolvConf: /etc/resolv.conf
rotateCertificates: true
runtimeRequestTimeout: 2m0s
serializeImagePulls: true
staticPodPath: /etc/kubernetes/manifests
streamingConnectionIdleTimeout: 4h0m0s
syncFrequency: 1m0s
volumeStatsAggPeriod: 1m0s

　啟動所有節點kubelet

systemctl daemon-reload
systemctl enable --now kubelet

此時系統日誌/var/log/messages顯示只有如下兩種資訊為正常，沒有迴圈列印日誌就是正常的，如下報錯資訊為cailico未安裝，安裝calico後即可恢復

Unable to update cni config: no networks found in /etc/cni/net.d

如果有很多報錯日誌，或者有大量看不懂的報錯，說明kubelet的配置有誤，需要檢查kubelet配置

檢視叢集狀態(Ready或NotReady都正常)

[root@k8s-master01 bootstrap]# kubectl get node

6.2 kube-proxy

注意，如果不是高可用叢集，10.103.236.236:8443改為master01的地址，8443改為apiserver的埠，預設是6443

以下操作只在Master01執行

cd /root/k8s-ha-install
kubectl -n kube-system create serviceaccount kube-proxy

kubectl create clusterrolebinding system:kube-proxy         --clusterrole system:node-proxier         --serviceaccount kube-system:kube-proxy

SECRET=$(kubectl -n kube-system get sa/kube-proxy \
    --output=jsonpath='{.secrets[0].name}')

JWT_TOKEN=$(kubectl -n kube-system get secret/$SECRET \
--output=jsonpath='{.data.token}' | base64 -d)

PKI_DIR=/etc/kubernetes/pki
K8S_DIR=/etc/kubernetes

kubectl config set-cluster kubernetes     --certificate-authority=/etc/kubernetes/pki/ca.pem     --embed-certs=true     --server=https://10.103.236.236:8443     --kubeconfig=${K8S_DIR}/kube-proxy.kubeconfig

kubectl config set-credentials kubernetes     --token=${JWT_TOKEN}     --kubeconfig=/etc/kubernetes/kube-proxy.kubeconfig

kubectl config set-context kubernetes     --cluster=kubernetes     --user=kubernetes     --kubeconfig=/etc/kubernetes/kube-proxy.kubeconfig

kubectl config use-context kubernetes     --kubeconfig=/etc/kubernetes/kube-proxy.kubeconfig

將kubeconfig傳送至其他節點

for NODE in k8s-master02 k8s-master03; do
     scp /etc/kubernetes/kube-proxy.kubeconfig  $NODE:/etc/kubernetes/kube-proxy.kubeconfig
 done
for NODE in k8s-node01 k8s-node02; do
     scp /etc/kubernetes/kube-proxy.kubeconfig $NODE:/etc/kubernetes/kube-proxy.kubeconfig
 done

所有節點新增kube-proxy的配置和service檔案：

vim /usr/lib/systemd/system/kube-proxy.service

[Unit]
Description=Kubernetes Kube Proxy
Documentation=https://github.com/kubernetes/kubernetes
After=network.target

[Service]
ExecStart=/usr/local/bin/kube-proxy \
  --config=/etc/kubernetes/kube-proxy.yaml \
  --v=2

Restart=always
RestartSec=10s

[Install]
WantedBy=multi-user.target

如果更改了叢集Pod的網段，需要更改kube-proxy.yaml的clusterCIDR為自己的Pod網段：以及mode=ipvs

vim /etc/kubernetes/kube-proxy.yaml

apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: 0.0.0.0
clientConnection:
  acceptContentTypes: ""
  burst: 10
  contentType: application/vnd.kubernetes.protobuf
  kubeconfig: /etc/kubernetes/kube-proxy.kubeconfig
  qps: 5
clusterCIDR: 172.16.0.0/12 
configSyncPeriod: 15m0s
conntrack:
  max: null
  maxPerCore: 32768
  min: 131072
  tcpCloseWaitTimeout: 1h0m0s
  tcpEstablishedTimeout: 24h0m0s
enableProfiling: false
healthzBindAddress: 0.0.0.0:10256
hostnameOverride: ""
iptables:
  masqueradeAll: false
  masqueradeBit: 14
  minSyncPeriod: 0s
  syncPeriod: 30s
ipvs:
  masqueradeAll: true
  minSyncPeriod: 5s
  scheduler: "rr"
  syncPeriod: 30s
kind: KubeProxyConfiguration
metricsBindAddress: 127.0.0.1:10249
mode: "ipvs"
nodePortAddresses: null
oomScoreAdj: -999
portRange: ""
udpIdleTimeout: 250ms

所有節點啟動kube-proxy

systemctl daemon-reload
systemctl enable --now kube-proxy

看下日誌如果出現如下所示表示正常

檢視svc，pod跟apiserver通訊都是走的如下地址

七、Calico安裝

建議安裝官方推薦版本

以下步驟只在master01執行

cd /root/k8s-ha-install/calico/

更改calico的網段，主要需要將紅色部分的網段，改為自己的Pod網段

cp calico.yaml calico.yaml.bak
sed -i "s#POD_CIDR#172.16.0.0/12#g" calico.yaml

#檢查
grep "IPV4POOL_CIDR" calico.yaml  -A 1

kubectl apply -f calico.yaml

#檢視容器狀態
kubectl get po -n kube-system

八、CoreDNS安裝

安裝官方推薦版本（推薦）

cd /root/k8s-ha-install/

如果更改了k8s service的網段需要將coredns的serviceIP改成k8s service網段的第十個IP

跟/etc/kubernetes/kubelet-conf.yml檔案中的一致

COREDNS_SERVICE_IP=`kubectl get svc | grep kubernetes | awk '{print $3}'`0
sed -i "s#KUBEDNS_SERVICE_IP#${COREDNS_SERVICE_IP}#g" CoreDNS/coredns.yaml

安裝coredns

 kubectl  create -f CoreDNS/coredns.yaml

安裝最新版CoreDNS（不推薦）

安裝k8s推薦的版本就行了，沒必要追求最新版本

COREDNS_SERVICE_IP=`kubectl get svc | grep kubernetes | awk '{print $3}'`0
git clone https://github.com/coredns/deployment.git
cd deployment/kubernetes
# ./deploy.sh -s -i ${COREDNS_SERVICE_IP} | kubectl apply -f -

檢視狀態
 # kubectl get po -n kube-system -l k8s-app=kube-dns

九、安裝Metrics Server

在新版的Kubernetes中系統資源的採集均使用Metrics-server，可以通過Metrics採集節點和Pod的記憶體、磁碟、CPU和網路的使用率。

k8s-ha-install目錄中有metrics-server跟kubeadm-metrics-server兩個目錄檔案，他們之間的區別對比.

vimdiff kubeadm-metrics-server/comp.yaml metrics-server/comp.yaml

可以發現只有證書部署位置不一樣，kubeadm自動生成的證書檔案是以.crt結尾的，二進位制cfssl生成的證書檔案是.pem結尾的，用的是之前生成的聚合證書。

安裝metrics server

cd /root/k8s-ha-install/metrics-server
kubectl  create -f .

等待metrics server啟動然後檢視狀態

# kubectl  top node
NAME           CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
k8s-master01   231m         5%     1620Mi          42%       
k8s-master02   274m         6%     1203Mi          31%       
k8s-master03   202m         5%     1251Mi          32%       
k8s-node01     69m          1%     667Mi           17%       
k8s-node02     73m          1%     650Mi           16%

十、安裝dashboard

Dashboard用於展示叢集中的各類資源，同時也可以通過Dashboard實時檢視Pod的日誌和在容器中執行一些命令等。

安裝指定版本dashboard（推薦）

cd /root/k8s-ha-install/dashboard/
kubectl  create -f .

檢視狀態

[root@k8s-master01 dashboard]# kubectl get po -n kubernetes-dashboard
NAME                                         READY   STATUS    RESTARTS   AGE
dashboard-metrics-scraper-7fcdff5f4c-kbvx8   1/1     Running   0          59s
kubernetes-dashboard-85f59f8ff7-25zrp        1/1     Running   0          59s

檢視暴露的埠號

[root@k8s-master01 dashboard]# kubectl get svc -n kubernetes-dashboard
NAME                        TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)         AGE
dashboard-metrics-scraper   ClusterIP   192.168.208.237   <none>        8000/TCP        98s
kubernetes-dashboard        NodePort    192.168.166.30    <none>        443:30812/TCP   98s

安裝最新版（可以研究一下）

官方GitHub地址：https://github.com/kubernetes/dashboard

可以在官方dashboard檢視到最新版dashboard

kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.3/aio/deploy/recommended.yaml
#地址改為頁面上最新的地址

建立管理員使用者

vim admin.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: admin-user
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding 
metadata: 
  name: admin-user
  annotations:
    rbac.authorization.kubernetes.io/autoupdate: "true"
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: admin-user
  namespace: kube-system
 
#應用yaml配置檔案
kubectl apply -f admin.yaml -n kube-system

登入dashboard參考kubeadm，如果是谷歌瀏覽器需要修改屬性。

更改dashboard的svc為NodePort，這樣可以使用宿主機加埠訪問到dashboard

kubectl edit svc kubernetes-dashboard -n kubernetes-dashboard
     29   selector:
     30     k8s-app: kubernetes-dashboard
     31   sessionAffinity: None
     32   type: NodePort #在32行的位置修改為NodePort

檢視埠號

[root@k8s-master01 dashboard]# kubectl get svc -n kubernetes-dashboard
NAME                        TYPE        CLUSTER-IP        EXTERNAL-IP   PORT(S)         AGE
dashboard-metrics-scraper   ClusterIP   192.168.208.237   <none>        8000/TCP        98s
kubernetes-dashboard        NodePort    192.168.166.30    <none>        443:30812/TCP   98s

訪問Dashboard：https://10.103.236.201:30812

關於token獲取，看kubeadm筆記。

十一、叢集驗證

注意：因為二進位制安裝master沒有配置汙點，是可以部署Pod的。

一個成功的叢集具備如下條件

Pod必須能解析Service\、
Pod必須能解析跨namespace的Service
每個節點都必須要能訪問Kubernetes的kubernetes svc 443和kube-dns的service 53
Pod和Pod之前要能通
1. 同namespace能通訊
2. 跨namespace能通訊
3. 跨機器能通訊

下面逐步驗證

#配置一個busybox
cat<<EOF | kubectl apply -f -
apiVersion: v1
kind: Pod
metadata:
  name: busybox
  namespace: default
spec:
  containers:
  - name: busybox
    image: busybox:1.28
    command:
      - sleep
      - "3600"
    imagePullPolicy: IfNotPresent
  restartPolicy: Always
EOF

kubectl get pod

參看是否能解析svc

[root@k8s-master01 dashboard]# kubectl exec  busybox -n default -- nslookup kubernetes
Server:    192.168.0.10
Address 1: 192.168.0.10 kube-dns.kube-system.svc.cluster.local

Name:      kubernetes
Address 1: 192.168.0.1 kubernetes.default.svc.cluster.local

檢視是否能解析跨namespace的Service

[root@k8s-master01 dashboard]# kubectl exec  busybox -n default -- nslookup kube-dns.kube-system
Server:    192.168.0.10
Address 1: 192.168.0.10 kube-dns.kube-system.svc.cluster.local

Name:      kube-dns.kube-system
Address 1: 192.168.0.10 kube-dns.kube-system.svc.cluster.local

所有節點測試是否能訪問443跟53埠

yum -y install telnet -y

[root@k8s-master01 dashboard]# kubectl get svc
NAME         TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)   AGE
kubernetes   ClusterIP   192.168.0.1   <none>        443/TCP   32h

telnet 192.168.0.1 443

#檢視kube-dns
[root@k8s-master01 dashboard]# kubectl get svc -n kube-system
NAME             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE
calico-typha     ClusterIP   192.168.229.37   <none>        5473/TCP                 29h
kube-dns         ClusterIP   192.168.0.10     <none>        53/UDP,53/TCP,9153/TCP   29h
metrics-server   ClusterIP   192.168.48.97    <none>        443/TCP                  12m

[root@k8s-master01 dashboard]# telnet 192.168.0.10 53
[root@k8s-master01 dashboard]# curl telnet 192.168.0.10:53
curl: (6) Could not resolve host: telnet; Unknown error
curl: (52) Empty reply from server #提示這個表示正常

#測試pod之間通訊
[root@k8s-master01 dashboard]# kubectl get po -n kube-system -owide
...省略...

[root@k8s-master01 dashboard]# kubectl get po -owide
NAME      READY   STATUS    RESTARTS   AGE     IP              NODE         NOMINATED NODE   READINESS GATES
busybox   1/1     Running   0          5m24s   172.27.14.193   k8s-node02   <none>           <none>
#進入這個容器，有些容器是沒有bash工具的進不了正常，換成busybox試試
kubectl exec -it busybox -- sh #或者
kubectl exec -it busybox -- bash
#注意如果進入系統元件容器要加名稱空間，如
kubectl exec -it calico-kube-coxxxx -n kube-system -- sh 
kubectl exec -it calico-kube-coxxxx -n kube-system -- bash

ping 其他節點

其他測試

#建立一個pod
kubectl run nginx --image=nginx
#建立一個deploy，有3個副本
kubectl create deploy nginx --image=nginx --replicas=3
kubectl get deploy
kubectl get po -owide #檢視這3個pod部署哪個節點上
#刪除
kubectl delete deploy nginx
kubectl delete po busybox nginx

十二、參考資料

基於世界500強的k8s實戰課程