一，kunernetes部署方式和環境介紹

1.1，生產環境可部署kubenetes集群的兩種方式

1.1.1 kubeadm

    kubeadm是k8s部署的一個工具，提供了kubeadm init和kubeadm join 用于快速部署k8s集群

1.1.2 二進制部署

從github上下載發行的版的kubernetes二進制包，手動部署每個組件，組成kubernetes集群
kubeadm降低了部署門檻，但是屏蔽了很多細節，但遇到問題比較難排查，如果想要更好的控制k8s集群推薦使用二進制的方式部署kubernetes集群，二進制部署相對來說是比較麻煩，部署的期間能學習很多工作原理，也比較有利于后期的維護。

1.2 部署kubernetes集群需要以下幾個條件：

1.一臺機器或者多臺機器，操作系統centos7.x-86_x64
2.硬件配置：master和node至少是2G內存或者更高的內存cpu至少2個甚至更多，硬盤50GB或者更多，資源少了啟動k8s集群可能會起不來
3.必須是可以訪問外網，在部署集群時需要拉取鏡像，如果不能上網需要提前下載好鏡像導入節點
4.禁止swap分區，k8s不支持swap分區。

1.3 環境準備

軟件環境：

軟件                 版本
操作系統：           centos7.6_x64
Docker              19.3-ce
Kubernetes          1.18

服務器規劃：

節點：            ip                                 組件                           
master： 10.0.0.11   kube-apiserver ,  kube-controller-manager kube-scheduler , etcd , docker
node01： 10.0.0.12   kubelet , kube-proxy , docker , etcd
node02:  10.0.0.13   kubelet , kube-proxy , docker , etcd

架構圖：

image.png

單master或者多master

1.4 系統初始化配置

關閉防火墻
systemctl stop firewalld
systemctl disable firewalld
關閉selinux
臨時關閉：
setenforce 0
永久關閉： 
sed -i 's/enforcing/disabled/' /etc/selinux/config
關閉swap分區
臨時關閉：
swapoff -a
永久關閉：
sed -ri 's/.*swap.*/#&/' /etc/fstab
主機名規劃設置 
hostnamectl set-hostname <name>
橋接的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  #生效
添加hosts文件
cat > /etc/hosts <<EOF
10.0.0.11 master
10.0.0.12 noed1
10.0.0.13 noed2
EOF
時間同步
yum install -y ntpdate
ntpdate time.windows.com

二， 部署etcd集群

etcd是一個分布式的鍵值存儲系統，kubernetes使用etcd進行數據存儲。所以要首先準備一個etcd的數據庫，為了解決單點的故障我們部署etcd時采用集群的方式部署這里使用3臺機器部署可以有一臺機器故障，也可以采用5臺機器有兩臺 可以有2臺機器故障

10.0.0.11    etcd1
10.0.0.12    etcd2
10.0.0.13    etcd3

為了節省機器，我們把與k8s節點的機器進行復用，也可以單獨部署k8s集群，apiserver能連接上就沒有問題。

2.1 準備cfssl證書生成工具

cfssl是一個開源的證書管理工具，使用json文件生成證書，相比openssl更方便使用

找一個服務器操作，我這里使用master節點
wget https://pkg.cfssl.org/R1.2/cfssl_linux-amd64
wget https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64
wget https://pkg.cfssl.org/R1.2/cfssl-certinfo_linux-amd64
chmod +x cfssl_linux-amd64 cfssljson_linux-amd64 cfssl-certinfo_linux-amd64
mv cfssl_linux-amd64 /usr/local/bin/cfssl
mv cfssljson_linux-amd64 /usr/local/bin/cfssljson
mv cfssl-certinfo_linux-amd64 /usr/bin/cfssl-certinfo

2.2 生成etcd證書

創建工作目錄
mkdir -p ~/TLS/{etcd,k8s}
cd TLS/etcd
自簽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": "Beijing",
            "ST": "Beijing"
        }
    ]
}
EOF

生成證書：

cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
[root@master etcd]# ll *.pem
-rw------- 1 root root 1679 Nov 14 11:09 ca-key.pem
-rw-r--r-- 1 root root 1265 Nov 14 11:09 ca.pem
使用自簽CA 簽發etcd HTTPS證書
創建證書申請文件：
cat > server-csr.json << EOF
{
    "CN": "etcd",
    "hosts": [
    "10.0.0.11",
    "10.0.0.12",
    "10.0.0.13"
    ],
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "BeiJing",
            "ST": "BeiJing"
        }
    ]
}
EOF
注：上述的hosts字段IP為所有節點etcd的集群內部通信IP一個都不能少，可以多預留幾個為方便以后擴容用。
生成證書：
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=www server-csr.json | cfssljson -bare server
[root@master etcd]# ll server*pem
-rw------- 1 root root 1679 Nov 14 11:17 server-key.pem
-rw-r--r-- 1 root root 1338 Nov 14 11:17 server.pem

2.3 從github下載二進制文件

下載地址：https://github.com/etcd-io/etcd/releases/download/v3.4.9/etcd-v3.4.9-linux-amd64.tar.gz

2.4 部署etcd集群

以下操作在節點1操作，簡化操作會將節點1生成的文件全部copy到節點2和節點3
創建目錄并解壓二進制包

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

創建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://10.0.0.11:2380"
ETCD_LISTEN_CLIENT_URLS="https://10.0.0.11:2379"
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://10.0.0.11:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://10.0.0.11:2379"
ETCD_INITIAL_CLUSTER="etcd-1=https://10.0.0.11:2380,etcd-2=https://10.0.0.12:2380,etcd-3=https://10.0.0.13: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_ADVERTISE_PEER_URLS：集群通告地址
ETCD_ADVERTISE_CLIENT_URLS：客戶端通告地址
ETCD_INITIAL_CLUSTER：集群節點地址
ETCD_INITIAL_CLUSTER_TOKEN：集群Token
ETCD_INITIAL_CLUSTER_STATE：加入集群的當前狀態，new是新集群，existing表示加入已有集群

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

copy剛剛生成的證書：

cp ~/TLS/etcd/ca*pem ~/TLS/etcd/server*pem /opt/etcd/ssl/

將上面的節點1所有生成的文件copy到節點2和節點3：

scp -r /opt/etcd/ root@10.0.0.12:/opt/
scp /usr/lib/systemd/system/etcd.service root@10.0.0.12:/usr/lib/systemd/system/
scp -r /opt/etcd/ root@10.0.0.13:/opt/
scp /usr/lib/systemd/system/etcd.service root@10.0.0.13:/usr/lib/systemd/system/

然后在節點2和節點3分別修改etcd.conf配置文件：

node1：
[root@node1 ~]# cat /opt/etcd/cfg/etcd.conf
#[Member]
ETCD_NAME="etcd-2"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://10.0.0.12:2380"
ETCD_LISTEN_CLIENT_URLS="https://10.0.0.12:2379"
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://10.0.0.12:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://10.0.0.12:2379"
ETCD_INITIAL_CLUSTER="etcd-1=https://10.0.0.11:2380,etcd-2=https://10.0.0.12:2380,etcd-3=https://10.0.0.13:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"
node2：
[root@node2 ~]# cat /opt/etcd/cfg/etcd.conf
#[Member]
ETCD_NAME="etcd-3"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://10.0.0.13:2380"
ETCD_LISTEN_CLIENT_URLS="https://10.0.0.13:2379"
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://10.0.0.13:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://10.0.0.13:2379"
ETCD_INITIAL_CLUSTER="etcd-1=https://10.0.0.11:2380,etcd-2=https://10.0.0.12:2380,etcd-3=https://10.0.0.13:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

然后啟動并開機自啟動：

systemctl daemon-reload
systemctl start etcd
systemctl enable etcd

查看集群狀態：

[root@master ~]# 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://10.0.0.11:2379,https://10.0.0.12:2379,https://10.0.0.13:2379" endpoint health
https://10.0.0.11:2379 is healthy: successfully committed proposal: took = 42.25622ms
https://10.0.0.13:2379 is healthy: successfully committed proposal: took = 47.996367ms
https://10.0.0.12:2379 is healthy: successfully committed proposal: took = 46.980311ms
輸出的是上面的信息就說明部署集群成功，如有不成功先看日志、var/log/messages或者journalctl -u etcd

三，安裝docker

下載地址：https://download.docker.com/linux/static/stable/x86_64/docker-19.03.9.tgz

以下在所有節點操作。這里采用二進制安裝，用yum安裝也一樣。

3.1 解壓二進制包

tar -xf docker-19.03.9.tgz
mv docker/* /usr/bin

3.2 system管理docker

cat > /usr/lib/systemd/system/docker.service << EOF
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network-online.target firewalld.service
Wants=network-online.target
[Service]
Type=notify
ExecStart=/usr/bin/dockerd
ExecReload=/bin/kill -s HUP $MAINPID
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TimeoutStartSec=0
Delegate=yes
KillMode=process
Restart=on-failure
StartLimitBurst=3
StartLimitInterval=60s
[Install]
WantedBy=multi-user.target
EOF

3.3 配置阿里云加速

mkdir /etc/docker
cat > /etc/docker/daemon.json << EOF
{
  "registry-mirrors": ["https://b9pmyelo.mirror.aliyuncs.com"]
}
EOF

3.4 啟動并設置開機自啟動

systemctl daemon-reload
systemctl start docker
systemctl enable docker

四，部署Master Node

4.1 生成kube-apiserver證書

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
生成證書：
[root@master ~]# cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
[root@master k8s]# ll *pem
-rw------- 1 root root 1679 Nov 14 16:05 ca-key.pem
-rw-r--r-- 1 root root 1359 Nov 14 16:05 ca.pem

2，使用自簽CA簽發kube-apiserver HTTPS證書
創建證書申請文件：

cat > server-csr.json << EOF
{
    "CN": "kubernetes",
    "hosts": [
      "10.0.0.1",
      "127.0.0.1",
      "10.0.0.11",
      "10.0.0.12",
      "10.0.0.13",
      "10.0.0.14",
      "10.0.0.15",
      "10.0.0.16",
      "10.0.0.17",
      "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
[root@master k8s]# ll server*pem
-rw------- 1 root root 1675 Nov 14 16:16 server-key.pem
-rw-r--r-- 1 root root 1659 Nov 14 16:16 server.pem

4.2 從github下載二進制文件

下載地址： https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.18.md#v1183

注：打開連接你會發現有很多包，只需要下載一個server包就好了，里面包含了master和woker node二進制文件

4.3 解壓二進制包

mkdir -p /opt/kubernetes/{bin,cfg,ssl,logs}
tar xf 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/

4.4 部署kube-apiserver

1，創建配置文件

cat > /opt/kubernetes/cfg/kube-apiserver.conf << EOF
KUBE_APISERVER_OPTS="--logtostderr=false \\
--v=2 \\
--log-dir=/opt/kubernetes/logs \\
--etcd-servers=https://10.0.0.11:2379,https://10.0.0.12:2379,https://10.0.0.13:2379 \\
--bind-address=10.0.0.11 \\
--secure-port=6443 \\
--advertise-address=10.0.0.11 \\
--allow-privileged=true \\
--service-cluster-ip-range=10.0.0.0/24 \\
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \\
--authorization-mode=RBAC,Node \\
--enable-bootstrap-token-auth=true \\
--token-auth-file=/opt/kubernetes/cfg/token.csv \\
--service-node-port-range=30000-32767 \\
--kubelet-client-certificate=/opt/kubernetes/ssl/server.pem \\
--kubelet-client-key=/opt/kubernetes/ssl/server-key.pem \\
--tls-cert-file=/opt/kubernetes/ssl/server.pem  \\
--tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \\
--client-ca-file=/opt/kubernetes/ssl/ca.pem \\
--service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \\
--etcd-cafile=/opt/etcd/ssl/ca.pem \\
--etcd-certfile=/opt/etcd/ssl/server.pem \\
--etcd-keyfile=/opt/etcd/ssl/server-key.pem \\
--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證書
--etcd-xxxfile：連接Etcd集群證書
--audit-log-xxx：審計日志

2，copy剛才生成的證書

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

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

image.png

創建上述配置文件找那個的token文件：

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

格式：token，用戶名，UID，用戶組
token也可自行生成替換：

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

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，啟動并設置開機自啟動

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

6，授權kubelet-bootstrap用戶允許請求證書：

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

4.5 部署kube-controller-manager

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 \\
--master=127.0.0.1:8080 \\
--bind-address=127.0.0.1 \\
--allocate-node-cidrs=true \\
--cluster-cidr=10.244.0.0/16 \\
--service-cluster-ip-range=10.0.0.0/24 \\
--cluster-signing-cert-file=/opt/kubernetes/ssl/ca.pem \\
--cluster-signing-key-file=/opt/kubernetes/ssl/ca-key.pem  \\
--root-ca-file=/opt/kubernetes/ssl/ca.pem \\
--service-account-private-key-file=/opt/kubernetes/ssl/ca-key.pem \\
--experimental-cluster-signing-duration=87600h0m0s"
EOF
--master：通過本地非安全本地端口8080連接apiserver
--leader-elect：當該組件啟動多個時自動選舉（HA）
--cluster-signing-cert-file/--cluster-signing-key-file：自動為kubelet頒發證書的CA，與apiserver保持一致

2，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

3.啟動并設置開機自啟動

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

4.6, 部署kube-scheduler

1.創建配置文件

cat > /opt/kubernetes/cfg/kube-scheduler.conf << EOF
KUBE_SCHEDULER_OPTS="--logtostderr=false \
--v=2 \
--log-dir=/opt/kubernetes/logs \
--leader-elect \
--master=127.0.0.1:8080 \
--bind-address=127.0.0.1"
EOF
--master：通過本地非安全本地端口8080連接apiserver。
--leader-elect：當該組件啟動多個時，自動選舉（HA）

2. 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

3. 啟動并設置開機啟動

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

4.查看集群狀態：
所有組件都已經啟動成功，通過kubectl工具查看當前集群組件狀態：

[root@master bin]# 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"} 

如上結果說明master節點組件運行正常。

五，部署Woker Node

下面還是在master節點上操作，也作為node節點

5.1 創建工作目錄

在所有woker節點創建工作目錄：

mkdir -p /opt/kubernetes/{bin,cfg,ssl,logs}
從master節點拷貝：
[root@master ~]# cd kubernetes/server/bin
[root@master bin]# cp kubelet kube-proxy /opt/kubernetes/bin

5.2部署kubelet

1，創建配置文件

cat > /opt/kubernetes/cfg/kubelet.conf << EOF
KUBELET_OPTS="--logtostderr=false \\
--v=2 \\
--log-dir=/opt/kubernetes/logs \\
--hostname-override=k8s-master \\
--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=lizhenliang/pause-amd64:3.0"
EOF
--hostname-override：顯示名稱，集群中唯一
--network-plugin：啟用CNI
--kubeconfig：空路徑，會自動生成，后面用于連接apiserver
--bootstrap-kubeconfig：首次啟動向apiserver申請證書
--config：配置參數文件
--cert-dir：kubelet證書生成目錄
--pod-infra-container-image：管理Pod網絡容器的鏡像

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

3，生成bootstrap.kubeconfig文件

KUBE_APISERVER="https://10.0.0.11:6443" # apiserver IP:PORT
TOKEN="c47ffb939f5ca36231d9e3121a252940" # 與token.csv里保持一致
# 生成 kubelet bootstrap kubeconfig 配置文件
kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=bootstrap.kubeconfig
kubectl config set-credentials "kubelet-bootstrap" \
  --token=${TOKEN} \
  --kubeconfig=bootstrap.kubeconfig
kubectl config set-context default \
  --cluster=kubernetes \
  --user="kubelet-bootstrap" \
  --kubeconfig=bootstrap.kubeconfig
kubectl config use-context default --kubeconfig=bootstrap.kubeconfig

拷貝到配置文件路徑：

[root@master bin]# cp bootstrap.kubeconfig /opt/kubernetes/cfg

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

5，啟動并設置開機自啟動

systemctl daemon-reload
systemctl start kubelet
systemctl enable kubelet

5.3，批準kubelet證書申請并加入集群

查看證書請求:

kubectl get csr
NAME                                                  AGE    SIGNERNAME                                    REQUESTOR          CONDITION
node-csr--G3jTzzjPOXVvyhS4Wt_UWvVr9YxHBSWVBjqbFD-dYo  2m4s  kubernetes.io/kube-apiserver-client-kubelet  kubelet-bootstrap  Pending

批準申請：

kubectl certificate approve node-csr--G3jTzzjPOXVvyhS4Wt_UWvVr9YxHBSWVBjqbFD-dYo

查看節點：

kubectl get nodes
NAME        STATUS    ROLES    AGE  VERSION
k8s-master  NotReady  <none>  37s  v1.18.3

注：由于還沒有部署網絡插件節點就會沒有準備就緒 NotReady

5.4 部署kube-proxy

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

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-master
clusterCIDR: 10.0.0.0/24
EOF

3,生成kube-proxy.kubeconfig文件
生成kube-proxy證書：
切換目錄：

cd /root/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
[root@master k8s]# ll kube-proxy*pem
-rw------- 1 root root 1679 Nov 14 17:19 kube-proxy-key.pem
-rw-r--r-- 1 root root 1403 Nov 14 17:19 kube-proxy.pem

生成kubeconfig文件：

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

拷貝配置文件到指定路徑：

cp kube-proxy.kubeconfig /opt/kubernetes/cfg/

4.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

5.啟動并配置開機自啟動

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

5.5 部署CNI網絡

先準備好CNI二進制文件：

下載地址：https://github.com/containernetworking/plugins/releases/download/v0.8.6/cni-plugins-linux-amd64-v0.8.6.tgz

解壓二進制包并移動到默認的工作目錄：

mkdir /opt/cni/bin -p
tar xf cni-plugins-linux-amd64-v0.8.6.tgz -C /opt/cni/bin/

部署CNI網絡：

wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
sed -i -r "s#quay.io/coreos/flannel:.*-amd64#registry.aliyuncs.com/google_containers/flannel:v0.12.0-amd64#g" kube-flannel.yml

默認地址無法訪問修改為docker hub鏡像地址

kubectl apply -f kube-flannel.yml
[root@master ~]# kubectl get pods -n kube-system
NAME                    READY  STATUS    RESTARTS  AGE
kube-flannel-ds-srtq4  1/1    Running  0          11m
[root@master ~]# kubectl get nodes
NAME        STATUS  ROLES    AGE  VERSION
k8s-master  Ready    <none>  31m  v1.18.3

5.6 授權apiserver訪問kubelet

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
[root@master ~]# kubectl apply -f apiserver-to-kubelet-rbac.yaml

5.7 新增加woker node

1，copy已經部署好餓node相關文件到新節點：
在master節點將Worker Node涉及文件拷貝到新節點10.0.0.12/13

node1：
scp -r /opt/kubernetes root@10.0.0.12:/opt/
scp -r /usr/lib/systemd/system/{kubelet,kube-proxy}.service root@10.0.0.12:/usr/lib/systemd/system
scp -r /opt/cni/ root@10.0.0.12:/opt/
scp -r /opt/kubernetes/ssl/ca.pem root@10.0.0.12:/opt/kubernetes/ssl
node2：
scp -r /opt/kubernetes root@10.0.0.13:/opt/
scp -r /usr/lib/systemd/system/{kubelet,kube-proxy}.service root@10.0.0.13:/usr/lib/systemd/system
scp -r /opt/cni/ root@10.0.0.13:/opt/
scp -r /opt/kubernetes/ssl/ca.pem root@10.0.0.13:/opt/kubernetes/ssl

2.刪除kubelet和kubeconfig文件：在node01和node02

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

注：這幾個文件上是證書申請后自動生成的，每個node節點都不同，所以必須刪除重新生成
3，修改主機名：node1和node2都要修改

[root@master ~]# vi /opt/kubernetes/cfg/kubelet.conf
--hostname-override=k8s-node1
[root@master ~]#  vi /opt/kubernetes/cfg/kube-proxy-config.yml
hostnameOverride: k8s-node1

4. 啟動并設置開機啟動

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

5. 在Master上批準新Node kubelet證書申請

[root@master ~]# kubectl get csr
NAME                                                  AGE  SIGNERNAME                                    REQUESTOR          CONDITION
node-csr--G3jTzzjPOXVvyhS4Wt_UWvVr9YxHBSWVBjqbFD-dYo  52m  kubernetes.io/kube-apiserver-client-kubelet  kubelet-bootstrap  Approved,Issued
node-csr-CyHqUAAsgTKpnPTNOxJWGissadNll5QEbQmiZ9wHjqg  60s  kubernetes.io/kube-apiserver-client-kubelet  kubelet-bootstrap  Pending
node-csr-tXc_pejNXrtq0LpMGW92RMoGwL54Bb47In4iI8kgerI  50s  kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap  Pending
[root@master ~]# kubectl certificate approve node-csr-CyHqUAAsgTKpnPTNOxJWGissadNll5QEbQmiZ9wHjqg
[root@master ~]# kubectl certificate approve node-csr-tXc_pejNXrtq0LpMGW92RMoGwL54Bb47In4iI8kgerI

6，查看node狀態：

[root@master ~]# kubectl get nodes
NAME        STATUS  ROLES    AGE    VERSION
k8s-master  Ready    <none>  4h3m  v1.18.3
k8s-node1   Ready    <none>  29m   v1.18.3
k8s-node2   Ready    <none>  29m   v1.18.3

7，安裝支持補全命令

yum install bash-completion -y
source /usr/share/bash-completion/bash_completion
source <(kubectl completion bash)
kubectl completion bash >/etc/bash_completion.d/kubectl

六、部署Dashboard和CoreDNS

6.1部署Dashboard

wget https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/recommended.yaml

默認Dashboard只能集群內部訪問，修改Service為NodePort類型，暴露到外部

vim recommended.yaml
kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
spec:
  ports:
    - port: 443
      targetPort: 8443
      nodePort: 30001
  type: NodePort
  selector:
    k8s-app: kubernetes-dashboard

kubectl apply -f recommended.yaml

[root@master ~]# kubectl get pods,svc -n kubernetes-dashboard 
NAME                                             READY   STATUS    RESTARTS   AGE
pod/dashboard-metrics-scraper-694557449d-49gsb   1/1     Running   0          69s
pod/kubernetes-dashboard-9774cc786-zpvnq         1/1     Running   0          69s

NAME                                TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)         AGE
service/dashboard-metrics-scraper   ClusterIP   10.0.0.183   <none>        8000/TCP        69s
service/kubernetes-dashboard        NodePort    10.0.0.56    <none>        443:30001/TCP   70s

訪問地址：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}')
Name:         dashboard-admin-token-ldkwm
Namespace:    kube-system
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: dashboard-admin
              kubernetes.io/service-account.uid: a19a7c1a-2e9a-40bd-a98d-070b12660907

Type:  kubernetes.io/service-account-token

Data
====
namespace:  11 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6IkpGXzZuME9hMVJBbm1vRVAwdHN1TlRlMVZyRTdwQmRCWjVmbE1ZVGpRZm8ifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkYXNoYm9hcmQtYWRtaW4tdG9rZW4tbGRrd20iLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGFzaGJvYXJkLWFkbWluIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiYTE5YTdjMWEtMmU5YS00MGJkLWE5OGQtMDcwYjEyNjYwOTA3Iiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmUtc3lzdGVtOmRhc2hib2FyZC1hZG1pbiJ9.uKLuCPIs2pXgiT3JyWXbjYDR00A3O6kACS2SlsbFSmBuVK4hcKx0dqitS8-Awp-rwICxbu28j3Pdcq2x_nkJPg6NluIz7OMkb7VDGITTDQNUL-XJ09Gb4QUMVO24VlpPHFUk_jObdbPHieLOgRlRtMGmwZxuBq5dtBMT831GNYO93we7mYky67csadrP1U-dN3L9Wos45qGqKlbveaTIOmnoxxd6oNzytOcTbchzzLB9FbccyX5PmSrUfOPmZtvyYk9ckwqnY_ROw4-Q_GQKNrC6FvFIrukUqZGMKKJBQ8YLiYvczTJfBtE8Ly54ZZJ0-aTh12JBKtS3zlD89fAY_A
ca.crt:     1359 bytes

使用輸出的token登錄dashboard

image.png

image.png

6.2部署CoreDNS

CoreDNS用于集群內部Service名稱解析。