k8s二進制安裝部署(詳細)-有解無憂

一、生產環境部署k8s常見的幾種方式

說明：文章內使用到的yaml可到博客資源內下載 k8s-yaml

1、kubeadm

Kubeadm是一個K8s部署工具，提供kubeadm init和kubeadm join，用于快速部署Kubernetes集群，

2、二進制

從github下載發行版的二進制包，手動部署每個組件，組成Kubernetes集群，
小結：  
Kubeadm降低部署門檻，但屏蔽了很多細節，遇到問題很難排查，如果想更容易可控，推薦使用二進制包部署Kubernetes集群，雖然手動部署
麻煩點，期間可以學習很多作業原理，也利于后期維護，

3、kubespray

Kubespray 是 Kubernetes incubator 中的專案，目標是提供 Production Ready Kubernetes 部署方案，該專案基礎是通過 Ansible Playbook 
來定義系統與 Kubernetes 集群部署的任務，

二、二進制部署

1、準備環境

服務器要求:

建議最小硬體配置: 2核CPU\2G記憶體\30G硬碟，
服務器最好可以訪問外網,會有從網上拉取鏡像的需求,如果服務器不能上網,需要提前下載對應鏡像匯入節點，

軟體環境:

軟體	版本
作業系統	CentOS7.x_x64(mini)
容器引擎	Docker Ce19
Kubernetes	Kubernetes V1.20

服務器規劃:

角色	IP	組件
k8s-master1	192.168.242.51	kube-apiserver,kube-controller-manager,kube-scheduler,kubelet,kube-proxy,docker,etcd,nginx,keepalived
k8s-master2	192.168.242.54	kube-apiserver,kube-controller-manager,kube-scheduler,kubelet,kube-proxy,docker,nginx,keepalived
k8s-node1	192.168.242.52	kubelet,kube-proxy,docker,etcd
k8s-node2	192.168.242.53	kubelet,kube-proxy,docker,etcd
負載均衡器(虛擬IP)	192.168.242.55

須知:

    考慮到有些朋友電腦配置較低,一次性開四臺虛擬機電腦跑不動, 所以搭建這套k8s高可用集群分兩部分實施,先部署一套單Master架構(三臺),  
    再擴容為多Master架構(4臺或6臺),  順便再熟悉下Master擴容流程，

單Master架構圖
在這里插入圖片描述
單Master服務器規劃:

角色	IP	組件
k8s-master	192.168.242.51	kube-apiserver,kube-controller-manager,kube-scheduler,etcd
k8s-node1	192.168.242.52	kubelet,kube-proxy,docker,etcd
k8s-node2	192.168.242.53	kubelet,kube-proxy,docker,etcd

2、作業系統初始化配置(所有節點)

#關閉系統防火墻
systemctl stop firewalld
systemctl disable firewalld

#關閉selinux
sed -i 's/enforcing/disabled/' /etc/selinux/config  #永久
setenforce 0  # 臨時 

#關閉swap
swapoff -a   #臨時
sed -ri 's/.*swap.*/#&/' /etc/fstab  #永久

#根據規劃設定主機名
hostnamectl set-hostname k8s-master1
hostnamectl set-hostname k8s-master2
hostnamectl set-hostname k8s-node1
hostnamectl set-hostname k8s-node2

#添加hosts
cat >> /etc/hosts << EOF
192.168.242.51 k8s-master1
192.168.242.52 k8s-node1
192.168.242.53 k8s-node2
192.168.242.54 k8s-master2
EOF

#將橋接的IPV4流量傳遞到iptables的鏈
cat > /etc/sysctl.d/k8s.conf << EOF 
net.bridge.bridge-nf-call-ip6tables = 1 
net.bridge.bridge-nf-call-iptables = 1 
EOF
sysctl --system  #生效

#時間同步
#使用阿里云時間服務器進行臨時同步
[root@k8s-node1 ~]# ntpdate ntp.aliyun.com
 4 Sep 21:27:49 ntpdate[22399]: adjust time server 203.107.6.88 offset 0.001010 sec

#如需配置NTP服務可參考該檔案
https://blog.csdn.net/qq_44078641/article/details/120071838

3、部署etcd集群

3.1 etcd簡介

Etcd 是一個分布式鍵值存盤系統，Kubernetes使用Etcd進行資料存盤，所以先準備一個Etcd資料庫，為解決Etcd單點故障，應采用集群方式部署，這里使用3臺組建集群，可容忍1臺機器故障，當然，你也可以使用5臺組建集群，可容忍2臺機器故障

3.2 服務器規劃

節點名稱	IP
etcd-1	192.168.242.51
etcd-2	192.168.242.52
etcd-2	192.168.242.53

說明:
為了節省機器,這里與k8s節點復用,也可以部署在k8s機器之外,只要apiserver能連接到就行，

3.3 cfssl證書生成工具準備

cfssl簡介:
cfssl是一個開源的證書管理工具，使用json檔案生成證書，相比openssl更方便使用，
找任意一臺服務器操作，這里用Master1節點，

#創建目錄存放cfssl工具
mkdir /software-cfssl

#下載相關工具
wget https://pkg.cfssl.org/R1.2/cfssl_linux-amd64 -P /software-cfssl/
wget https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64 -P /software-cfssl/
wget https://pkg.cfssl.org/R1.2/cfssl-certinfo_linux-amd64 -P /software-cfssl/

cd /software-cfssl/
chmod +x *
cp cfssl_linux-amd64 /usr/local/bin/cfssl
cp cfssljson_linux-amd64 /usr/local/bin/cfssljson
cp cfssl-certinfo_linux-amd64 /usr/bin/cfssl-certinfo

說明:
如果下載失敗,可以使用檔案中附件 cfssl工具包

3.4 自簽證書頒發機構(CA)

3.4.1 創建作業目錄

mkdir -p ~/TLS/{etcd,k8s}
cd ~/TLS/etcd/

3.4.2 生成自簽CA配置

cat > ca-config.json << EOF
{
  "signing": {
    "default": {
      "expiry": "87600h"
    },
    "profiles": {
      "www": {
         "expiry": "87600h",
         "usages": [
            "signing",
            "key encipherment",
            "server auth",
            "client auth"
        ]
      }
    }
  }
}
EOF

cat > ca-csr.json << EOF
{
    "CN": "etcd CA",
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "YuMingYu",
            "ST": "YuMingYu"
        }
    ]
}
EOF

3.4.3 生成自簽CA證書

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

說明:
當前目錄下會生成 ca.pem和ca-key.pem檔案

[root@k8s-master1 etcd]# ls .
ca-config.json  ca.csr  ca-csr.json  ca-key.pem  ca.pem

3.5 使用自簽CA簽發etcd https證書

3.5.1 創建證書申請檔案

cat > server-csr.json << EOF
{
    "CN": "etcd",
    "hosts": [
    "192.168.242.51",
    "192.168.242.52",
    "192.168.242.53",
    "192.168.242.54"
    ],
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "YuMingYu",
            "ST": "YuMingYu"
        }
    ]
}
EOF

說明:
上述檔案hosts欄位中ip為所有etcd節點的集群內部通信ip,一個都不能少,為了方便后期擴容可以多寫幾個預留的ip，

3.5.2 生成證書

cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=www server-csr.json | cfssljson -bare server

說明:
當前目錄下會生成 server.pem 和 server-key.pem

[root@k8s-master1 etcd]# ls
ca-config.json  ca-csr.json  ca.pem      server-csr.json  server.pem
ca.csr          ca-key.pem   server.csr  server-key.pem

3.6 下載etcd二進制檔案

下載地址

#下載后上傳到服務器任意位置即可
https://github.com/etcd-io/etcd/releases/download/v3.4.9/etcd-v3.4.9-linux-amd64.tar.gz

說明:
如果下載有問題,可使用附件中的檔案，

3.7 部署etcd集群

以下操作在master1上面操作,為簡化操作,待會將master1節點生成的所有檔案拷貝到其他節點，

3.7.1 創建作業目錄并解壓二進制包

mkdir /opt/etcd/{bin,cfg,ssl} -p
tar -xf etcd-v3.4.9-linux-amd64.tar.gz
mv etcd-v3.4.9-linux-amd64/{etcd,etcdctl} /opt/etcd/bin/

3.8 創建etcd組態檔

cat > /opt/etcd/cfg/etcd.conf << EOF
#[Member]
ETCD_NAME="etcd-1"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.242.51:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.242.51:2379"

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.242.51:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.242.51:2379"
ETCD_INITIAL_CLUSTER="etcd-1=https://192.168.242.51:2380,etcd-2=https://192.168.242.52:2380,etcd-3=https://192.168.242.53:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"
EOF

配置說明:

ETCD_NAME：節點名稱,集群中唯一
ETCD_DATA_DIR：資料目錄
ETCD_LISTEN_PEER_URLS：集群通訊監聽地址
ETCD_LISTEN_CLIENT_URLS：客戶端訪問監聽地址
ETCD_INITIAL_CLUSTER：集群節點地址
ETCD_INITIALCLUSTER_TOKEN：集群Token
ETCD_INITIALCLUSTER_STATE：加入集群的狀態：new是新集群,existing表示加入已有集群

3.9 systemd管理etcd

cat > /usr/lib/systemd/system/etcd.service << EOF
[Unit]
Description=Etcd Server
After=network.target
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
EnvironmentFile=/opt/etcd/cfg/etcd.conf
ExecStart=/opt/etcd/bin/etcd \
--cert-file=/opt/etcd/ssl/server.pem \
--key-file=/opt/etcd/ssl/server-key.pem \
--peer-cert-file=/opt/etcd/ssl/server.pem \
--peer-key-file=/opt/etcd/ssl/server-key.pem \
--trusted-ca-file=/opt/etcd/ssl/ca.pem \
--peer-trusted-ca-file=/opt/etcd/ssl/ca.pem \
--logger=zap
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
EOF

3.10 將master1節點所有生成的檔案拷貝到節點2和節點3

for i in {2..3}
do
scp -r /opt/etcd/ root@192.168.242.5$i:/opt/
scp /usr/lib/systemd/system/etcd.service root@192.168.242.5$i:/usr/lib/systemd/system/
done

3.11 修改節點2，節點3 ,etcd.conf組態檔中的節點名稱和當前服務器IP:

#[Member]
ETCD_NAME="etcd-1"    #節點2修改為: etcd-2 節點3修改為: etcd-3
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.242.51:2380"  #修改為對應節點IP
ETCD_LISTEN_CLIENT_URLS="https://192.168.242.51:2379"  #修改為對應節點IP

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.242.51:2380" #修改為對應節點IP
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.242.51:2379" #修改為對應節點IP
ETCD_INITIAL_CLUSTER="etcd-1=https://192.168.242.51:2380,etcd-2=https://192.168.242.52:2380,etcd-3=https://192.168.242.53:2380"  
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

3.12 啟動etcd并設定開機自啟

說明:
etcd須多個節點同時啟動,不然執行systemctl start etcd會一直卡在前臺,連接其他節點,建議通過批量管理工具,或者腳本同時啟動etcd，

systemctl daemon-reload
systemctl start etcd
systemctl enable etcd

3.13 檢查etcd集群狀態

[root@k8s-master1 ~]# ETCDCTL_API=3 /opt/etcd/bin/etcdctl --cacert=/opt/etcd/ssl/ca.pem --cert=/opt/etcd/ssl/server.pem --key=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.242.51:2379,https://192.168.242.52:2379,https://192.168.242.53:2379" endpoint health --write-out=table
+-----------------------------+--------+-------------+-------+
|          ENDPOINT           | HEALTH |    TOOK     | ERROR |
+-----------------------------+--------+-------------+-------+
| https://192.168.242.52:2379 |   true | 67.267851ms |       |
| https://192.168.242.51:2379 |   true | 67.374967ms |       |
| https://192.168.242.53:2379 |   true | 69.244918ms |       |
+-----------------------------+--------+-------------+-------+

如果為以上狀態證明部署的沒有問題

3.14 etcd問題排查(日志)

less /var/log/message
journalctl -u etcd

4、安裝Docker(所有節點)

這里使用Docker作為容器引擎,也可以換成別的,例如containerd,k8s在1.20版本就不在支持docker

4.1 解壓二進制包

wget https://download.docker.com/linux/static/stable/x86_64/docker-19.03.9.tgz
tar -xf docker-19.03.9.tgz
mv docker/* /usr/bin/

4.2 配置鏡像加速

sudo mkdir -p /etc/docker
sudo tee /etc/docker/daemon.json <<-'EOF'
{
  "registry-mirrors": ["https://3s9106.mirror.alncs.com"]
}
EOF

說明:
可參考: https://blog.csdn.net/qq_44078641/article/details/104366373

4.3 啟動并設定開機啟動

systemctl daemon-reload
systemctl start docker
systemctl enable docker

5、部署Master節點

5.1 生成kube-apiserver證書

5.1.1 自簽證書頒發機構(CA)

cd ~/TLS/k8s

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 -

目錄下會生成 ca.pem 和 ca-key.pem

5.1.2 使用自簽CA簽發kube-apiserver https證書

創建證書申請檔案：

cat > server-csr.json << EOF
{
    "CN": "kubernetes",
    "hosts": [
      "10.0.0.1",
      "127.0.0.1",
      "192.168.242.51",
      "192.168.242.52",
      "192.168.242.53",
      "192.168.242.54",
      "192.168.242.55",
      "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

說明:
上述檔案中hosts欄位中IP為所有Master/LB/VIP IP,一個都不能少,為了方便后期擴容可以多寫幾個預留的IP，

生成證書:

cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes server-csr.json | cfssljson -bare server

說明：
當前目錄下會生成server.pem 和 server-key.pem檔案，

5.2 下載

下載地址:
https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.20.md
在這里插入圖片描述

5.3 解壓二進制包

上傳剛才下載的k8s軟體包到服務器上

mkdir -p /opt/kubernetes/{bin,cfg,ssl,logs} 
tar zxvf kubernetes-server-linux-amd64.tar.gz
cd kubernetes/server/bin
cp kube-apiserver kube-scheduler kube-controller-manager /opt/kubernetes/bin
cp kubectl /usr/bin/

5.4 部署kube-apiserver

5.4.1 創建組態檔

cat > /opt/kubernetes/cfg/kube-apiserver.conf << EOF
KUBE_APISERVER_OPTS="--logtostderr=false \\
--v=2 \\
--log-dir=/opt/kubernetes/logs \\
--etcd-servers=https://192.168.242.51:2379,https://192.168.242.52:2379,https://192.168.242.53:2379 \\
--bind-address=192.168.242.51 \\
--secure-port=6443 \\
--advertise-address=192.168.242.51 \\
--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 \\
--service-account-issuer=api \\
--service-account-signing-key-file=/opt/kubernetes/ssl/server-key.pem \\
--etcd-cafile=/opt/etcd/ssl/ca.pem \\
--etcd-certfile=/opt/etcd/ssl/server.pem \\
--etcd-keyfile=/opt/etcd/ssl/server-key.pem \\
--requestheader-client-ca-file=/opt/kubernetes/ssl/ca.pem \\
--proxy-client-cert-file=/opt/kubernetes/ssl/server.pem \\
--proxy-client-key-file=/opt/kubernetes/ssl/server-key.pem \\
--requestheader-allowed-names=kubernetes \\
--requestheader-extra-headers-prefix=X-Remote-Extra- \\
--requestheader-group-headers=X-Remote-Group \\
--requestheader-username-headers=X-Remote-User \\
--enable-aggregator-routing=true \\
--audit-log-maxage=30 \\
--audit-log-maxbackup=3 \\
--audit-log-maxsize=100 \\
--audit-log-path=/opt/kubernetes/logs/k8s-audit.log"
EOF

說明:
上面兩個\\第一個是轉義符,第二個是換行符,使用轉義符是為了使用EOF保留換行符，

--logtostderr ：啟用日志
--v ：日志等級
--log-dir ：日志目錄
--etcd-servers ：etcd集群地址
--bind-address ：監聽地址
--secure-port ：https安全埠
--advertise-address ：集群通告地址
--allow-privileged ：啟動授權
--service-cluster-ip-range ：Service虛擬IP地址段
--enable-admission-plugins ：準入控制模塊
--authorization-mode ：認證授權,啟用RBAC授權和節點自管理
--enable-bootstrap-token-auth ：啟用TLS bootstrap機制
--token-auth-file ：bootstrap token檔案
--service-node-port-range ：Service nodeport型別默認分配埠范圍
--kubelet-client-xxx ：apiserver訪問kubelet客戶端證書
--tls-xxx-file ：apiserver https證書
1.20版本必須加的引數：--service-account-issuer,--service-account-signing-key-file
--etcd-xxxfile ：連接etcd集群證書
--audit-log-xxx ：審計日志
啟動聚合層網關配置：--requestheader-client-ca-file,--proxy-client-cert-file,--proxy-client-key-file,--requestheader-allowed-names,--requestheader-extra-headers-prefix,--requestheader-group-headers,--requestheader-username-headers,--enable-aggregator-routing

5.4.2 拷貝剛才生成的證書

把剛才生成的證書拷貝到組態檔中的路徑：

cp ~/TLS/k8s/ca*pem ~/TLS/k8s/server*pem /opt/kubernetes/ssl/

5.4.3 啟用TLS bootstrapping機制

TLS Bootstraping：Master apiserver啟用TLS認證后，Node節點kubelet和kube-proxy要與kube-apiserver進行通信，必須使用CA簽發的有效證書才可以，當Node節點很多時，這種客戶端證書頒發需要大量作業，同樣也會增加集群擴展復雜度，為了簡化流程，Kubernetes引入了TLS bootstraping機制來自動頒發客戶端證書，kubelet會以一個低權限用戶自動向apiserver申請證書，kubelet的證書由apiserver動態簽署，所以強烈建議在Node上使用這種方式，目前主要用于kubelet，kube-proxy還是由我們統一頒發一個證書，
TLS bootstraping 作業流程：
在這里插入圖片描述

創建上述組態檔中token檔案：

cat > /opt/kubernetes/cfg/token.csv << EOF
4136692876ad4b01bb9dd0988480ebba,kubelet-bootstrap,10001,"system:node-bootstrapper"
EOF

格式：token,用戶名,UID,用戶組

token也可自行生成替換：

head -c 16 /dev/urandom | od -An -t x | tr -d ' '

5.4.4 systemd管理apiserver

cat > /usr/lib/systemd/system/kube-apiserver.service << EOF
[Unit]
Description=Kubernetes API Server
Documentation=https://github.com/kubernetes/kubernetes

[Service]
EnvironmentFile=/opt/kubernetes/cfg/kube-apiserver.conf
ExecStart=/opt/kubernetes/bin/kube-apiserver \$KUBE_APISERVER_OPTS
Restart=on-failure

[Install]
WantedBy=multi-user.target
EOF

5.4.5 啟動并設定開機啟動

systemctl daemon-reload
systemctl start kube-apiserver 
systemctl enable kube-apiserver

5.5 部署kube-controller-manager

5.5.1 創建組態檔

cat > /opt/kubernetes/cfg/kube-controller-manager.conf << EOF
KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=false \\
--v=2 \\
--log-dir=/opt/kubernetes/logs \\
--leader-elect=true \\
--kubeconfig=/opt/kubernetes/cfg/kube-controller-manager.kubeconfig \\
--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 \\
--cluster-signing-duration=87600h0m0s"
EOF

--kubeconfig ：連接apiserver組態檔，
--leader-elect ：當該組件啟動多個時,自動選舉(HA)
--cluster-signing-cert-file ：自動為kubelet頒發證書的CA,apiserver保持一致
--cluster-signing-key-file ：自動為kubelet頒發證書的CA,apiserver保持一致

5.5.2 生成kubeconfig檔案

生成kube-controller-manager證書：

# 切換作業目錄
cd ~/TLS/k8s

# 創建證書請求檔案
cat > kube-controller-manager-csr.json << EOF
{
  "CN": "system:kube-controller-manager",
  "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 kube-controller-manager-csr.json | cfssljson -bare kube-controller-manager

生成kubeconfig檔案(以下是shell命令,直接在shell終端執行)

KUBE_CONFIG="/opt/kubernetes/cfg/kube-controller-manager.kubeconfig"
KUBE_APISERVER="https://192.168.242.51:6443"

kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-credentials kube-controller-manager \
  --client-certificate=./kube-controller-manager.pem \
  --client-key=./kube-controller-manager-key.pem \
  --embed-certs=true \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user=kube-controller-manager \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config use-context default --kubeconfig=${KUBE_CONFIG}

5.5.3 systemd管理controller-manager

cat > /usr/lib/systemd/system/kube-controller-manager.service << EOF
[Unit]
Description=Kubernetes Controller Manager
Documentation=https://github.com/kubernetes/kubernetes

[Service]
EnvironmentFile=/opt/kubernetes/cfg/kube-controller-manager.conf
ExecStart=/opt/kubernetes/bin/kube-controller-manager \$KUBE_CONTROLLER_MANAGER_OPTS
Restart=on-failure

[Install]
WantedBy=multi-user.target
EOF

5.5.4 啟動并設定開機自啟

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

5.6 部署 kube-scheduler

5.6.1 創建組態檔

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

--kubeconfig ：連接apiserver組態檔
--leader-elect ：當該組件啟動多個時,自動選舉(HA)，

5.6.2 生成kubeconfig檔案

生成kube-scheduler證書：

# 切換作業目錄
cd ~/TLS/k8s

# 創建證書請求檔案
cat > kube-scheduler-csr.json << EOF
{
  "CN": "system:kube-scheduler",
  "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 kube-scheduler-csr.json | cfssljson -bare kube-scheduler

生成kubeconfig檔案：

KUBE_CONFIG="/opt/kubernetes/cfg/kube-scheduler.kubeconfig"
KUBE_APISERVER="https://192.168.242.51:6443"

kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-credentials kube-scheduler \
  --client-certificate=./kube-scheduler.pem \
  --client-key=./kube-scheduler-key.pem \
  --embed-certs=true \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user=kube-scheduler \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config use-context default --kubeconfig=${KUBE_CONFIG}

5.6.3 systemd管理scheduler

cat > /usr/lib/systemd/system/kube-scheduler.service << EOF
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes

[Service]
EnvironmentFile=/opt/kubernetes/cfg/kube-scheduler.conf
ExecStart=/opt/kubernetes/bin/kube-scheduler \$KUBE_SCHEDULER_OPTS
Restart=on-failure

[Install]
WantedBy=multi-user.target
EOF

5.6.4 啟動并設定開機啟動

systemctl daemon-reload
systemctl start kube-scheduler
systemctl enable kube-scheduler

5.6.5 查看集群狀態

生成kubectl連接集群的證書：

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

生成kubeconfig檔案：

mkdir /root/.kube

KUBE_CONFIG="/root/.kube/config"
KUBE_APISERVER="https://192.168.242.51:6443"

kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-credentials cluster-admin \
  --client-certificate=./admin.pem \
  --client-key=./admin-key.pem \
  --embed-certs=true \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user=cluster-admin \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config use-context default --kubeconfig=${KUBE_CONFIG}

通過kubectl工具查看當前集群組件狀態：

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

如上說明Master節點組件運行正常，

5.6.6 授權kubelet-bootstrap用戶允許請求證書

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

6、部署Work Node

下面還是在master node上面操作,即當Master節點,也當Work Node節點

6.1 創建作業目錄并拷貝二進制檔案

注: 在所有work node創建作業目錄

mkdir -p /opt/kubernetes/{bin,cfg,ssl,logs}

從master節點k8s-server軟體包中拷貝到所有work節點:

#進入到k8s-server軟體包目錄
cd /k8s-software/kubernetes/server/bin/

for i in {1..3}
do
scp kubelet  kube-proxy root@192.168.242.5$i:/opt/kubernetes/bin/
done

6.2 部署kubelet

6.2.1 創建組態檔

cat > /opt/kubernetes/cfg/kubelet.conf << EOF
KUBELET_OPTS="--logtostderr=false \\
--v=2 \\
--log-dir=/opt/kubernetes/logs \\
--hostname-override=k8s-master1 \\
--network-plugin=cni \\
--kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \\
--bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \\
--config=/opt/kubernetes/cfg/kubelet-config.yml \\
--cert-dir=/opt/kubernetes/ssl \\
--pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0"
EOF

--hostname-override ：顯示名稱,集群唯一(不可重復)，
--network-plugin ：啟用CNI，
--kubeconfig ：空路徑,會自動生成,后面用于連接apiserver，
--bootstrap-kubeconfig ：首次啟動向apiserver申請證書，
--config ：組態檔引數，
--cert-dir ：kubelet證書目錄，
--pod-infra-container-image ：管理Pod網路容器的鏡像 init container

6.2.2 組態檔

cat > /opt/kubernetes/cfg/kubelet-config.yml << EOF
kind: KubeletConfiguration
apiVersion: kubelet.config.k8s.io/v1beta1
address: 0.0.0.0
port: 10250
readOnlyPort: 10255
cgroupDriver: cgroupfs
clusterDNS:
- 10.0.0.2
clusterDomain: cluster.local 
failSwapOn: false
authentication:
  anonymous:
    enabled: false
  webhook:
    cacheTTL: 2m0s
    enabled: true
  x509:
    clientCAFile: /opt/kubernetes/ssl/ca.pem 
authorization:
  mode: Webhook
  webhook:
    cacheAuthorizedTTL: 5m0s
    cacheUnauthorizedTTL: 30s
evictionHard:
  imagefs.available: 15%
  memory.available: 100Mi
  nodefs.available: 10%
  nodefs.inodesFree: 5%
maxOpenFiles: 1000000
maxPods: 110
EOF

6.2.3 生成kubelet初次加入集群引導kubeconfig檔案

KUBE_CONFIG="/opt/kubernetes/cfg/bootstrap.kubeconfig"
KUBE_APISERVER="https://192.168.242.51:6443" # apiserver IP:PORT
TOKEN="4136692876ad4b01bb9dd0988480ebba" # 與token.csv里保持一致  /opt/kubernetes/cfg/token.csv 

# 生成 kubelet bootstrap kubeconfig 組態檔
kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-credentials "kubelet-bootstrap" \
  --token=${TOKEN} \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user="kubelet-bootstrap" \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config use-context default --kubeconfig=${KUBE_CONFIG}

6.2.4 systemd管理kubelet

cat > /usr/lib/systemd/system/kubelet.service << EOF
[Unit]
Description=Kubernetes Kubelet
After=docker.service

[Service]
EnvironmentFile=/opt/kubernetes/cfg/kubelet.conf
ExecStart=/opt/kubernetes/bin/kubelet \$KUBELET_OPTS
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
EOF

6.2.5 啟動并設定開機啟動

systemctl daemon-reload
systemctl start kubelet
systemctl enable kubelet

6.2.6 允許kubelet證書申請并加入集群

#查看kubelet證書請求
[root@k8s-master1 bin]# kubectl get csr
NAME                                                   AGE    SIGNERNAME                                    REQUESTOR           CONDITION
node-csr-KbHieprZUMOvTFMHGQ1RNTZEhsSlT5X6wsh2lzfUry4   107s   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Pending

#允許kubelet節點申請
[root@k8s-master1 bin]# kubectl certificate approve  node-csr-KbHieprZUMOvTFMHGQ1RNTZEhsSlT5X6wsh2lzfUry4
certificatesigningrequest.certificates.k8s.io/node-csr-KbHieprZUMOvTFMHGQ1RNTZEhsSlT5X6wsh2lzfUry4 approved

#查看申請
[root@k8s-master1 bin]# kubectl get csr
NAME                                                   AGE     SIGNERNAME                                    REQUESTOR           CONDITION
node-csr-KbHieprZUMOvTFMHGQ1RNTZEhsSlT5X6wsh2lzfUry4   2m35s   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Approved,Issued

#查看節點
[root@k8s-master1 bin]# kubectl get nodes
NAME          STATUS     ROLES    AGE     VERSION
k8s-master1   NotReady   <none>   2m11s   v1.20.10

說明：
由于網路插件還沒有部署,節點會沒有準備就緒NotReady

6.3 部署kube-proxy

6.3.1 創建組態檔

cat > /opt/kubernetes/cfg/kube-proxy.conf << EOF
KUBE_PROXY_OPTS="--logtostderr=false \\
--v=2 \\
--log-dir=/opt/kubernetes/logs \\
--config=/opt/kubernetes/cfg/kube-proxy-config.yml"
EOF

6.3.2 配置引數檔案

cat > /opt/kubernetes/cfg/kube-proxy-config.yml << EOF
kind: KubeProxyConfiguration
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: 0.0.0.0
metricsBindAddress: 0.0.0.0:10249
clientConnection:
  kubeconfig: /opt/kubernetes/cfg/kube-proxy.kubeconfig
hostnameOverride: k8s-master1
clusterCIDR: 10.244.0.0/16
EOF

6.3.3 生成kube-proxy證書檔案

# 切換作業目錄
cd ~/TLS/k8s

# 創建證書請求檔案
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

6.3.4 生成kube-proxy.kubeconfig檔案

KUBE_CONFIG="/opt/kubernetes/cfg/kube-proxy.kubeconfig"
KUBE_APISERVER="https://192.168.242.51:6443"

kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-credentials kube-proxy \
  --client-certificate=./kube-proxy.pem \
  --client-key=./kube-proxy-key.pem \
  --embed-certs=true \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user=kube-proxy \
  --kubeconfig=${KUBE_CONFIG}
  
kubectl config use-context default --kubeconfig=${KUBE_CONFIG}

6.3.5 systemd管理kube-proxy

cat > /usr/lib/systemd/system/kube-proxy.service << EOF
[Unit]
Description=Kubernetes Proxy
After=network.target

[Service]
EnvironmentFile=/opt/kubernetes/cfg/kube-proxy.conf
ExecStart=/opt/kubernetes/bin/kube-proxy \$KUBE_PROXY_OPTS
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
EOF

6.3.6 啟動并設定開機自啟

systemctl daemon-reload
systemctl start kube-proxy
systemctl enable kube-proxy

6.4 部署網路組件(Calico)

Calico是一個純三層的資料中心網路方案，是目前Kubernetes主流的網路方案，

kubectl apply -f calico.yaml
kubectl get pods -n kube-system

等Calico Pod都Running,節點也會準備就緒，

[root@k8s-master1 yaml]# kubectl get pods -n kube-system
NAME                                      READY   STATUS    RESTARTS   AGE
calico-kube-controllers-97769f7c7-zcz5d   1/1     Running   0          3m11s
calico-node-5tnll                         1/1     Running   0          3m11s

[root@k8s-master1 yaml]# kubectl get nodes
NAME          STATUS   ROLES    AGE   VERSION
k8s-master1   Ready    <none>   21m   v1.20.10

6.5 授權apiserver訪問kubelet

應用場景：如kubectl logs

cat > apiserver-to-kubelet-rbac.yaml << EOF
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  annotations:
    rbac.authorization.kubernetes.io/autoupdate: "true"
  labels:
    kubernetes.io/bootstrapping: rbac-defaults
  name: system:kube-apiserver-to-kubelet
rules:
  - apiGroups:
      - ""
    resources:
      - nodes/proxy
      - nodes/stats
      - nodes/log
      - nodes/spec
      - nodes/metrics
      - pods/log
    verbs:
      - "*"
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: system:kube-apiserver
  namespace: ""
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: system:kube-apiserver-to-kubelet
subjects:
  - apiGroup: rbac.authorization.k8s.io
    kind: User
    name: kubernetes
EOF

kubectl apply -f apiserver-to-kubelet-rbac.yaml

7、新增加Work Node

7.1 拷貝以部署好的相關檔案到新節點

在Master節點將Work Node涉及檔案拷貝到新節點 242.52/242.53

for i in {2..3}; do scp -r /opt/kubernetes root@192.168.242.5$i:/opt/; done

for i in {2..3}; do scp -r /usr/lib/systemd/system/{kubelet,kube-proxy}.service root@192.168.242.5$i:/usr/lib/systemd/system; done

for i in {2..3}; do scp -r /opt/kubernetes/ssl/ca.pem root@192.168.242.5$i:/opt/kubernetes/ssl/; done

7.2 洗掉kubelet證書和kubeconfig檔案

rm -f /opt/kubernetes/cfg/kubelet.kubeconfig 
rm -f /opt/kubernetes/ssl/kubelet*

說明:
這幾個檔案是證書申請審批后自動生成的,每個Node不同,必須洗掉，

7.3 修改主機名

vi /opt/kubernetes/cfg/kubelet.conf
--hostname-override=k8s-node1

vi /opt/kubernetes/cfg/kube-proxy-config.yml
hostnameOverride: k8s-node1

7.4 啟動并設定開機自啟

systemctl daemon-reload
systemctl start kubelet kube-proxy
systemctl enable kubelet kube-proxy

7.5 在Master上同意新的Node kubelet證書申請

#查看證書請求
[root@k8s-master1 kubernetes]# kubectl get csr
NAME                                                   AGE   SIGNERNAME                                    REQUESTOR           CONDITION
node-csr-2vKShQc_wlqPrTPAwT5MHpdRWIX-oyr9NyBXu1XNwxg   12s   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Pending
node-csr-KbHieprZUMOvTFMHGQ1RNTZEhsSlT5X6wsh2lzfUry4   47h   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Approved,Issued
#同意
[root@k8s-master1 kubernetes]# kubectl certificate approve node-csr-2vKShQc_wlqPrTPAwT5MHpdRWIX-oyr9NyBXu1XNwxg
certificatesigningrequest.certificates.k8s.io/node-csr-2vKShQc_wlqPrTPAwT5MHpdRWIX-oyr9NyBXu1XNwxg approved

7.6 查看Node狀態(要稍等會才會變成ready,會下載一些初始化鏡像)

[root@k8s-master1 kubernetes]# kubectl get nodes
NAME          STATUS   ROLES    AGE   VERSION
k8s-master1   Ready    <none>   46h   v1.20.10
k8s-node1     Ready    <none>   77s   v1.20.10

說明:
其他節點同上

8、部署Dashboard和CoreDNS

8.1 部署Dashboard

kubectl apply -f kubernetes-dashboard.yaml

#查看部署情況
[root@k8s-master1 yaml]#  kubectl get pods,svc -n kubernetes-dashboard
NAME                                             READY   STATUS    RESTARTS   AGE
pod/dashboard-metrics-scraper-7b59f7d4df-k49t9   1/1     Running   0          10m
pod/kubernetes-dashboard-74d688b6bc-l9jz4        1/1     Running   0          10m

NAME                                TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)         AGE
service/dashboard-metrics-scraper   ClusterIP   10.0.0.206   <none>        8000/TCP        10m
service/kubernetes-dashboard        NodePort    10.0.0.10    <none>        443:30001/TCP   10m

訪問地址: https://NodeIP:30001
創建service account并系結默認cluster-admin管理員集群角色

kubectl create serviceaccount dashboard-admin -n kube-system
kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin
kubectl describe secrets -n kube-system $(kubectl -n kube-system get secret | awk '/dashboard-admin/{print $1}')

使用輸出的token登陸Dashboard(如訪問提示https例外,可使用火狐瀏覽器)
在這里插入圖片描述

在這里插入圖片描述

8.2 部署CoreDNS

CoreDNS主要用于集群內部Service名稱決議，

[root@k8s-master1 yaml]# kubectl apply -f coredns.yaml 

[root@k8s-master1 yaml]# kubectl get pods -n kube-system
NAME                                      READY   STATUS    RESTARTS   AGE
calico-kube-controllers-97769f7c7-zcz5d   1/1     Running   1          47h
calico-node-5tnll                         1/1     Running   1          47h
calico-node-m8sdg                         1/1     Running   0          42m
calico-node-pqvk9                         1/1     Running   0          56m
coredns-6cc56c94bd-5hvfb                  1/1     Running   0          37s

測驗決議是否正常

[root@k8s-master1 yaml]# kubectl run -it --rm dns-test --image=busybox:1.28.4 sh 
If you don't see a command prompt, try pressing enter.
/ # ns
nsenter   nslookup
/ # nslookup kubernetes
Server:    10.0.0.2
Address 1: 10.0.0.2 kube-dns.kube-system.svc.cluster.local

至此一個單Master的k8s節點就已經完成了

9、增加Master節點(高可用架構)

說明:
Kubernetes作為容器集群系統，通過健康檢查+重啟策略實作了Pod故障自我修復能力，通過調度演算法實作將Pod分布式部署，并保持預期副本數，根據Node失效狀態自動在其他Node拉起Pod，實作了應用層的高可用性，
針對Kubernetes集群，高可用性還應包含以下兩個層面的考慮：Etcd資料庫的高可用性和Kubernetes Master組件的高可用性，而Etcd我們已經采用3個節點組建集群實作高可用，本節將對Master節點高可用進行說明和實施，
Master節點扮演著總控中心的角色，通過不斷與作業節點上的Kubelet和kube-proxy進行通信來維護整個集群的健康作業狀態，如果Master節點故障，將無法使用kubectl工具或者API做任何集群管理，
Master節點主要有三個服務kube-apiserver、kube-controller-manager和kube-scheduler，其中kube-controller-manager和kube-scheduler組件自身通過選擇機制已經實作了高可用，所以Master高可用主要針對kube-apiserver組件，而該組件是以HTTP API提供服務，因此對他高可用與Web服務器類似，增加負載均衡器對其負載均衡即可，并且可水平擴容，

多Master架構圖
在這里插入圖片描述

9.1 部署Master2 Node

說明：
現在需要再增加一臺新服務器，作為Master2 Node，IP是192.168.242.54，
Master2 與已部署的Master1所有操作一致，所以我們只需將Master1所有K8s檔案拷貝過來，再修改下服務器IP和主機名啟動即可，

9.1.1 安裝Docker(Master1)

scp /usr/bin/docker* root@192.168.242.54:/usr/bin
scp /usr/bin/runc root@192.168.242.54:/usr/bin
scp /usr/bin/containerd* root@192.168.242.54:/usr/bin
scp /usr/lib/systemd/system/docker.service root@192.168.242.54:/usr/lib/systemd/system
scp -r /etc/docker root@192.168.242.54:/etc

9.1.2 啟動Docker、設定開機自啟(Master2)

systemctl daemon-reload
systemctl start docker
systemctl enable docker

9.1.3 創建etcd證書目錄(Master2)

mkdir -p /opt/etcd/ssl

9.1.4 拷貝檔案(Master1)

拷貝Master1上所有k8s檔案和etcd證書到Master2:

scp -r /opt/kubernetes root@192.168.242.54:/opt
scp -r /opt/etcd/ssl root@192.168.242.54:/opt/etcd
scp /usr/lib/systemd/system/kube* root@192.168.242.54:/usr/lib/systemd/system
scp /usr/bin/kubectl  root@192.168.242.54:/usr/bin
scp -r ~/.kube root@192.168.242.54:~

9.1.5 洗掉證書(Master2)

洗掉kubelet和kubeconfig檔案

rm -f /opt/kubernetes/cfg/kubelet.kubeconfig 
rm -f /opt/kubernetes/ssl/kubelet*

9.1.6 修改組態檔和主機名(Master2)

修改apiserver、kubelet和kube-proxy組態檔為本地IP：

vi /opt/kubernetes/cfg/kube-apiserver.conf 
...
--bind-address=192.168.242.54 \
--advertise-address=192.168.242.54 \
...

vi /opt/kubernetes/cfg/kube-controller-manager.kubeconfig
server: https://192.168.242.54:6443

vi /opt/kubernetes/cfg/kube-scheduler.kubeconfig
server: https://192.168.242.54:6443

vi /opt/kubernetes/cfg/kubelet.conf
--hostname-override=k8s-master2

vi /opt/kubernetes/cfg/kube-proxy-config.yml
hostnameOverride: k8s-master2

vi ~/.kube/config
...
server: https://192.168.242.54:6443

9.1.7 啟動并設定開機自啟(Master2)

systemctl daemon-reload
systemctl start kube-apiserver kube-controller-manager kube-scheduler kubelet kube-proxy
systemctl enable kube-apiserver kube-controller-manager kube-scheduler kubelet kube-proxy

9.1.7 查看集群狀態(Master2)

kubectl get cs
NAME                STATUS    MESSAGE             ERROR
scheduler             Healthy   ok                  
controller-manager       Healthy   ok                  
etcd-1               Healthy   {"health":"true"}   
etcd-2               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}

9.1.8 審批kubelet證書申請

# 查看證書請求
[root@k8s-master1 ~]# kubectl get csr
NAME                                                   AGE   SIGNERNAME                                    REQUESTOR           CONDITION
node-csr-EQoVFfTbo6DcvcWfaRzBbMst4BXmdyds99DEYk2oDDE   33m   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Pending

# 同意請求
kubectl certificate approve node-csr-EQoVFfTbo6DcvcWfaRzBbMst4BXmdyds99DEYk2oDDEcertificatesigningrequest.certificates.k8s.io/node-csr-EQoVFfTbo6DcvcWfaRzBbMst4BXmdyds99DEYk2oDDE approved

# 查看Node
[root@k8s-master1 ~]# kubectl get nodes
NAME          STATUS   ROLES    AGE     VERSION
k8s-master1   Ready    <none>   6d23h   v1.20.10
k8s-master2   Ready    <none>   9m11s   v1.20.10
k8s-node1     Ready    <none>   5d      v1.20.10
k8s-node2     Ready    <none>   5d      v1.20.10

至此一個雙Master節點k8s集群已經部署完畢

9.2 部署Nginx+Keepalived高可用負載均衡器

在這里插入圖片描述

Nginx是一個主流Web服務和反向代理服務器，這里用四層實作對apiserver實作負載均衡，
Keepalived是一個主流高可用軟體，基于VIP系結實作服務器雙機熱備，在上述拓撲中，Keepalived主要根據Nginx運行狀態判斷是否需要故障轉移（漂移VIP），例如當Nginx主節點掛掉，VIP會自動系結在Nginx備節點，從而保證VIP一直可用，實作Nginx高可用，
如果你是在公有云上，一般都不支持keepalived，那么你可以直接用它們的負載均衡器產品，直接負載均衡多臺Master kube-apiserver，架構與上面一樣，
在兩臺Master節點操作，

9.2.1 安裝軟體包(Master1/Master2)

yum install epel-release -y
yum install nginx keepalived -y

9.2.2 Nginx組態檔(主備相同)

cat > /etc/nginx/nginx.conf << "EOF"
user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log;
pid /run/nginx.pid;

include /usr/share/nginx/modules/*.conf;

events {
    worker_connections 1024;
}

# 四層負載均衡，為兩臺Master apiserver組件提供負載均衡
stream {

    log_format  main  '$remote_addr $upstream_addr - [$time_local] $status $upstream_bytes_sent';

    access_log  /var/log/nginx/k8s-access.log  main;

    upstream k8s-apiserver {
       server 192.168.242.51:6443;   # Master1 APISERVER IP:PORT
       server 192.168.242.54:6443;   # Master2 APISERVER IP:PORT
    }
    
    server {
       listen 16443; # 由于nginx與master節點復用，這個監聽埠不能是6443，否則會沖突
       proxy_pass k8s-apiserver;
    }
}

http {
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;

    sendfile            on;
    tcp_nopush          on;
    tcp_nodelay         on;
    keepalive_timeout   65;
    types_hash_max_size 2048;

    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;

    server {
        listen       80 default_server;
        server_name  _;

        location / {
        }
    }
}
EOF

9.2.3 keepalived組態檔(Master1)

cat > /etc/keepalived/keepalived.conf << EOF
global_defs { 
   notification_email { 
     acassen@firewall.loc 
     failover@firewall.loc 
     sysadmin@firewall.loc 
   } 
   notification_email_from Alexandre.Cassen@firewall.loc  
   smtp_server 127.0.0.1 
   smtp_connect_timeout 30 
   router_id NGINX_MASTER
} 

vrrp_script check_nginx {
    script "/etc/keepalived/check_nginx.sh"
}

vrrp_instance VI_1 { 
    state MASTER 
    interface ens33  # 修改為實際網卡名
    virtual_router_id 51 # VRRP 路由 ID實體，每個實體是唯一的 
    priority 100    # 優先級，備服務器設定 90 
    advert_int 1    # 指定VRRP 心跳包通告間隔時間，默認1秒 
    authentication { 
        auth_type PASS      
        auth_pass 1111 
    }  
    # 虛擬IP
    virtual_ipaddress { 
        192.168.242.55/24
    } 
    track_script {
        check_nginx
    } 
}
EOF

vrrp_script：指定檢查nginx作業狀態腳本（根據nginx狀態判斷是否故障轉移）
virtual_ipaddress：虛擬IP（VIP）

準備上述組態檔中檢查Nginx運行狀態的腳本

cat > /etc/keepalived/check_nginx.sh  << "EOF"
#!/bin/bash
count=$(ss -antp |grep 16443 |egrep -cv "grep|$$")

if [ "$count" -eq 0 ];then
    exit 1
else
    exit 0
fi
EOF
chmod +x /etc/keepalived/check_nginx.sh

9.2.4 keepalived配置(master2)

cat > /etc/keepalived/keepalived.conf << EOF
global_defs { 
   notification_email { 
     acassen@firewall.loc 
     failover@firewall.loc 
     sysadmin@firewall.loc 
   } 
   notification_email_from Alexandre.Cassen@firewall.loc  
   smtp_server 127.0.0.1 
   smtp_connect_timeout 30 
   router_id NGINX_BACKUP
} 

vrrp_script check_nginx {
    script "/etc/keepalived/check_nginx.sh"
}

vrrp_instance VI_1 { 
    state BACKUP 
    interface ens33
    virtual_router_id 51 # VRRP 路由 ID實體，每個實體是唯一的 
    priority 90
    advert_int 1
    authentication { 
        auth_type PASS      
        auth_pass 1111 
    }  
    virtual_ipaddress { 
        192.168.242.55/24
    } 
    track_script {
        check_nginx
    } 
}
EOF

準備上述組態檔中檢查nginx運行狀態的腳本：

cat > /etc/keepalived/check_nginx.sh  << "EOF"
#!/bin/bash
count=$(ss -antp |grep 16443 |egrep -cv "grep|$$")

if [ "$count" -eq 0 ];then
    exit 1
else
    exit 0
fi
EOF

chmod +x /etc/keepalived/check_nginx.sh

說明：
keepalived根據腳本回傳狀態碼（0為作業正常，非0不正常）判斷是否故障轉移，

9.2.5 Nginx增加Steam模塊

9.2.5.1 查看Nginx版本模塊

如果已經安裝 --with-stream模塊,后面的步驟可以跳過

[root@k8s-master2 nginx-1.20.1]# nginx -V
nginx version: nginx/1.20.1
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) 
configure arguments: --prefix=/usr/share/nginx --sbin-path=/usr/sbin/nginx --modules-path=/usr/lib64/nginx/modules --conf-path=/etc/nginx/nginx.conf --with-stream

9.2.5.2 下載同一個版本的nginx

下載地址 : http://nginx.org/download/

9.2.5.3 備份原Nginx檔案

mv /usr/sbin/nginx /usr/sbin/nginx.bak
cp -r /etc/nginx{,.bak}

9.2.5.3 重新編譯Nginx

檢查模塊是否支持，比如這次添加 limit 限流模塊 和 stream 模塊：
./configure –help | grep limit

ps：-without-http_limit_conn_module disable 表示已有該模塊，編譯時，不需要添加

./configure –help | grep stream

ps：–with-stream enable 表示不支持，編譯時要自己添加該模塊

根據第1步查到已有的模塊，加上本次需新增的模塊: --with-stream

編譯環境準備

yum -y install libxml2 libxml2-dev libxslt-devel 
yum -y install gd-devel 
yum -y install perl-devel perl-ExtUtils-Embed 
yum -y install GeoIP GeoIP-devel GeoIP-data
yum -y install pcre-devel
yum -y install openssl openssl-devel
yum -y install gcc make

編譯

tar -xf nginx-1.20.1.tar.gz
cd nginx-1.20.1/
./configure --prefix=/usr/share/nginx --sbin-path=/usr/sbin/nginx --modules-path=/usr/lib64/nginx/modules --conf-path=/etc/nginx/nginx.conf  --with-stream
make

說明:
make完成后不要繼續輸入“make install”，以免現在的nginx出現問題
以上完成后，會在objs目錄下生成一個nginx檔案，先驗證:

[root@k8s-master2 nginx-1.20.1]# ./objs/nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

9.2.5.4 替換nginx到Master1/Master2

cp ./objs/nginx /usr/sbin/ 
scp objs/nginx root@192.168.242.51:/usr/sbin/

9.2.5.5 修改nginx服務檔案

vim /usr/lib/systemd/system/nginx.service
[Unit]
Description=The nginx HTTP and reverse proxy server
After=network.target remote-fs.target nss-lookup.target
[Service]
Type=forking
PIDFile=/run/nginx.pid
ExecStartPre=/usr/bin/rm -rf /run/nginx.pid
ExecStartPre=/usr/sbin/nginx -t
ExecStart=/usr/sbin/nginx
ExecStop=/usr/sbin/nginx -s stop
ExecReload=/usr/sbin/nginx -s reload
PrivateTmp=true
[Install]
WantedBy=multi-user.target

9.2.6 啟動并設定開機自啟(master1/master2)

systemctl daemon-reload
systemctl start nginx keepalived
systemctl enable nginx keepalived

9.2.7 查看keepalived作業狀態

[root@k8s-master1 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:40:1a:d8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.242.51/24 brd 192.168.242.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet 192.168.242.55/24 scope global secondary ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe40:1ad8/64 scope link 
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:f3:e1:d2:e6 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
4: tunl0@NONE: <NOARP,UP,LOWER_UP> mtu 1440 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0
    inet 10.244.159.128/32 brd 10.244.159.128 scope global tunl0
       valid_lft forever preferred_lft forever
5: calia231fca418b@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1440 qdisc noqueue state UP group default 
    link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::ecee:eeff:feee:eeee/64 scope lin

可以看到，在ens33網卡系結了192.168.242.55 虛擬IP，說明作業正常，

9.2.8 Nginx+keepalived高可用測驗

關閉主節點Nginx，測驗VIP是否漂移到備節點服務器，
在Nginx Master執行 pkill nginx;
在Nginx Backup，ip addr命令查看已成功系結VIP，

9.2.9 訪問負載均衡器測驗

找K8s集群中任意一個節點，使用curl查看K8s版本測驗，使用VIP訪問：

[root@k8s-master1 ~]# curl -k https://192.168.242.55:16443/version
{
  "major": "1",
  "minor": "20",
  "gitVersion": "v1.20.10",
  "gitCommit": "8152330a2b6ca3621196e62966ef761b8f5a61bb",
  "gitTreeState": "clean",
  "buildDate": "2021-08-11T18:00:37Z",
  "goVersion": "go1.15.15",
  "compiler": "gc",
  "platform": "linux/amd64"
}[root@k8s-master1 ~]# curl -k https://192.168.242.55:16443/version
^[[A{
  "major": "1",
  "minor": "20",
  "gitVersion": "v1.20.10",
  "gitCommit": "8152330a2b6ca3621196e62966ef761b8f5a61bb",
  "gitTreeState": "clean",
  "buildDate": "2021-08-11T18:00:37Z",
  "goVersion": "go1.15.15",
  "compiler": "gc",
  "platform": "linux/amd64"
}[root@k8s-master1 ~]# curl -k https://192.168.242.55:16443/version
{
  "major": "1",
  "minor": "20",
  "gitVersion": "v1.20.10",
  "gitCommit": "8152330a2b6ca3621196e62966ef761b8f5a61bb",
  "gitTreeState": "clean",
  "buildDate": "2021-08-11T18:00:37Z",
  "goVersion": "go1.15.15",
  "compiler": "gc",
  "platform": "linux/amd64"
}[root@k8s-master1 ~]# curl -k https://192.168.242.55:16443/version
{
  "major": "1",
  "minor": "20",
  "gitVersion": "v1.20.10",
  "gitCommit": "8152330a2b6ca3621196e62966ef761b8f5a61bb",
  "gitTreeState": "clean",
  "buildDate": "2021-08-11T18:00:37Z",
  "goVersion": "go1.15.15",
  "compiler": "gc",
  "platform": "linux/amd64"

可以正確獲取到K8s版本資訊，說明負載均衡器搭建正常，該請求資料流程：curl -> vip(nginx) -> apiserver
通過查看Nginx日志也可以看到轉發apiserver IP：

[root@k8s-master1 ~]# tailf /var/log/nginx/k8s-access.log 
192.168.242.51 192.168.242.51:6443 - [14/Sep/2021:23:53:07 +0800] 200 424
192.168.242.51 192.168.242.54:6443 - [14/Sep/2021:23:53:09 +0800] 200 424
192.168.242.51 192.168.242.51:6443 - [14/Sep/2021:23:53:10 +0800] 200 424
192.168.242.51 192.168.242.54:6443 - [14/Sep/2021:23:53:11 +0800] 200 424

9.3 修改所有的Work Node連接LB VIP

試想下，雖然我們增加了Master2 Node和負載均衡器，但是我們是從單Master架構擴容的，也就是說目前所有的Worker Node組件連接都還是Master1 Node，如果不改為連接VIP走負載均衡器，那么Master還是單點故障，
因此接下來就是要改所有Worker Node（kubectl get node命令查看到的節點）組件組態檔，由原來192.168.242.51修改為192.168.242.55（VIP），
在所有Worker Node執行：

sed -i 's#192.168.242.51:6443#192.168.242.55:16443#' /opt/kubernetes/cfg/*
systemctl restart kubelet kube-proxy

檢查節點狀態

[root@k8s-master1 ~]# kubectl get nodes
NAME          STATUS   ROLES    AGE    VERSION
k8s-master1   Ready    <none>   7d     v1.20.10
k8s-master2   Ready    <none>   90m    v1.20.10
k8s-node1     Ready    <none>   5d1h   v1.20.10
k8s-node2     Ready    <none>   5d1h   v1.20.10

至此,一套高可用的k8s二進制可用集群就部署完成了~

三、部署常見問題

1、系統斷電后,某個etcd節點無法啟動

1.1 報錯資訊

publish error: etcdserver: request timed out

1.2 解決方法(如果沒有重要資料,或者剛進行完初始化)

檢查日志發現并沒有特別明顯的錯誤，根據經驗來講，etcd 節點壞掉一個其實對集群沒有大的影響，這時集群已經可以正常使用了，但是這個壞掉的 etcd 節點并沒有啟動

#進入 etcd 的資料存盤目錄進行備份 備份原有資料：
cd /var/lib/etcd/default.etcd/member/
cp * /data/bak/
#洗掉這個目錄下的所有資料檔案
rm -rf /var/lib/etcd/default.etcd/member/*
#停止另外兩臺 etcd 節點，因為 etcd 節點啟動時需要所有節點一起啟動，啟動成功后即可使用，
systemctl stop etcd
systemctl restart etcd

轉載請註明出處，本文鏈接：https://www.uj5u.com/ruanti/300710.html

標籤：其他

上一篇：阿里云前端[Vue.js / nuxt.js]?后端【node.js + mySql + PM2 +GIt】上線部署流程

下一篇：一個服務器、一個域名、一個docker、一個nginx、兩個jar包、兩個埠（玩轉二級域名）