採用二進制方式安裝K8S集羣，版本etcd-v3.3.10，flannel-v0.11.0，kubernetes-server-linux-amd64

時間 2019-11-11

標籤採用二進制方式安裝 k8s 集羣版本 etcd v3.3.10 flannel v0.11.0 kubernetes server linux amd64 amd 欄目負載均衡简体版

原文原文鏈接

官方提供的幾種Kubernetes部署方式

minikube

Minikube是一個工具，能夠在本地快速運行一個單點的Kubernetes，嘗試Kubernetes或平常開發的用戶使用。不能用於生產環境。node

官方地址：https://kubernetes.io/docs/setup/minikube/linux

kubeadm

Kubeadm也是一個工具，提供kubeadm init和kubeadm join，用於快速部署Kubernetes集羣。nginx

官方地址：https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/git

二進制包

從官方下載發行版的二進制包，手動部署每一個組件，組成Kubernetes集羣。github

小結：
生產環境中部署Kubernetes集羣，只有Kubeadm和二進制包可選，Kubeadm下降部署門檻，但屏蔽了不少細節，遇到問題很難排查。咱們這裏使用二進制包部署Kubernetes集羣，我也是推薦你們使用這種方式，雖然手動部署麻煩點，但學習不少工做原理，更有利於後期維護。docker

環境介紹

軟件環境
軟件版本
操做系統 CentOS 7.6_x64
Docker 18-ce
Kubernetes 1.12shell

服務器角色
角色 IP 組件
master 192.168.75.64 kube-apiserver，kube-controller-manager，kube-scheduler，etcd
node1 192.168.75.65 kubelet，kube-proxy，docker，flannel，etcd
node2 192.168.75.66 kubelet，kube-proxy，docker，flannel，etcdjson

初始化：
關閉selinux
關閉防火牆bootstrap

組件使用的證書
etcd ca.pem，server.pem，server-key.pem
flannel ca.pem，server.pem，server-key.pem
kube-apiserver ca.pem，server.pem，server-key.pem
kubelet ca.pem，ca-key.pem
kube-proxy ca.pem，kube-proxy.pem，kube-proxy-key.pem
kubectl ca.pem，admin.pem，admin-key.pemwindows

注意事項：
三臺主機的時間要儘量的同步，保持一致，不然日誌中會出現以下提示：

Nov  1 09:13:42 bogon etcd: the clock difference against peer e4ba0635cb718aa3 is too high [1.321146676s > 1s]
Nov  1 09:13:42 bogon etcd: the clock difference against peer e4ba0635cb718aa3 is too high [1.316524004s > 1s]
Nov  1 09:13:57 bogon etcd: the clock difference against peer a3174a13e9f88ee8 is too high [1.139050363s > 1s]
Nov  1 09:13:57 bogon etcd: the clock difference against peer a3174a13e9f88ee8 is too high [1.143273312s > 1s]

三臺主機使用公共的同步時間服務器，或者指定其中一臺服務器做爲同步時間服務器，另外兩臺從這臺進行時間同步

time.windows.com

再注意：
flannel v0.11 不支持etcd v3用法

部署Etcd集羣

三臺主機都須要部署etcd

1. 使用cfssl來生成自簽證書，先下載cfssl工具：

使用shell腳本：cfssl.sh

或者手動執行以下命令

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

這三個命令保存壓縮包：cfssl證書生成命令.7z

2. 生成證書

使用shell腳本：etcd-cert.sh

或者手動執行以下命令

建立如下三個文件：

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

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

# cat server-csr.json
# 注意： hosts主機參數要根據實際狀況進行修改
{
    "CN": "etcd",
    "hosts": [
    "192.168.75.64",
    "192.168.75.65",
    "192.168.75.66"
    ],
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "BeiJing",
            "ST": "BeiJing"
        }
    ]
}

# 生成證書
cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=www server-csr.json | cfssljson -bare server

# 查看證書
# ls *pem
ca-key.pem  ca.pem  server-key.pem  server.pem

證書這塊知道怎麼生成、怎麼用便可，建議暫時沒必要過多研究

3. 部署Etcd

二進制包下載地址：https://github.com/coreos/etcd/releases

如下部署步驟在規劃的三個etcd節點操做同樣，惟一不一樣的是etcd配置文件中的服務器IP要寫當前的，ETCD_NAME也要寫當前的

# 解壓二進制包
mkdir /opt/etcd/{bin,cfg,ssl} -p
tar zxvf etcd-v3.3.10-linux-amd64.tar.gz
cp etcd-v3.3.10-linux-amd64/{etcd,etcdctl} /opt/etcd/bin/

# 建立etcd配置文件

# cat /opt/etcd/cfg/etcd

#[Member]
ETCD_NAME="etcd01"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.75.64:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.75.64:2379"

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.75.64:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.75.64:2379"
ETCD_INITIAL_CLUSTER="etcd01=https://192.168.75.64:2380,etcd02=https://192.168.75.65:2380,etcd03=https://192.168.75.66:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

#[Security]
ETCD_CERT_FILE="/opt/etcd/ssl/server.pem"
ETCD_KEY_FILE="/opt/etcd/ssl/server-key.pem"
ETCD_TRUSTED_CA_FILE="/opt/etcd/ssl/ca.pem"
ETCD_CLIENT_CERT_AUTH="true"
ETCD_PEER_CERT_FILE="/opt/etcd/ssl/server.pem"
ETCD_PEER_KEY_FILE="/opt/etcd/ssl/server-key.pem"
ETCD_PEER_TRUSTED_CA_FILE="/opt/etcd/ssl/ca.pem"
ETCD_PEER_CLIENT_CERT_AUTH="true"

etcd配置文件說明：

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 
[Unit]
Description=Etcd Server
After=network.target
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
EnvironmentFile=/opt/etcd/cfg/etcd
ExecStart=/opt/etcd/bin/etcd
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target

# 把剛纔生成的證書拷貝到配置文件中的位置
cp ca.pem server*pem /opt/etcd/ssl

# 啓動並設置開啓啓動：
systemctl start etcd
systemctl enable etcd

ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub root@192.168.75.65
ssh-copy-id -i ~/.ssh/id_rsa.pub root@192.168.75.66

# 傳輸給其餘node節點

# 須要修改配置文件
scp -r /opt/etcd/ root@192.168.75.65:/opt/
scp -r /opt/etcd/ root@192.168.75.66:/opt/


scp /usr/lib/systemd/system/etcd.service root@192.168.75.65:/usr/lib/systemd/system/
scp /usr/lib/systemd/system/etcd.service root@192.168.75.66:/usr/lib/systemd/system/

# 啓動
systemctl daemon-reload
systemctl start etcd
systemctl enable etcd

# 三個配置文件示例

# 192.168.75.64
#[Member]
ETCD_NAME="etcd01"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.75.64:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.75.64:2379"

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.75.64:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.75.64:2379"
ETCD_INITIAL_CLUSTER="etcd01=https://192.168.75.64:2380,etcd02=https://192.168.75.65:2380,etcd03=https://192.168.75.66:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

#[Security]
ETCD_CERT_FILE="/opt/etcd/ssl/server.pem"
ETCD_KEY_FILE="/opt/etcd/ssl/server-key.pem"
ETCD_TRUSTED_CA_FILE="/opt/etcd/ssl/ca.pem"
ETCD_CLIENT_CERT_AUTH="true"
ETCD_PEER_CERT_FILE="/opt/etcd/ssl/server.pem"
ETCD_PEER_KEY_FILE="/opt/etcd/ssl/server-key.pem"
ETCD_PEER_TRUSTED_CA_FILE="/opt/etcd/ssl/ca.pem"
ETCD_PEER_CLIENT_CERT_AUTH="true"

# 192.168.75.65
#[Member]
ETCD_NAME="etcd02"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.75.65:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.75.65:2379"

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.75.65:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.75.65:2379"
ETCD_INITIAL_CLUSTER="etcd01=https://192.168.75.64:2380,etcd02=https://192.168.75.65:2380,etcd03=https://192.168.75.66:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

#[Security]
ETCD_CERT_FILE="/opt/etcd/ssl/server.pem"
ETCD_KEY_FILE="/opt/etcd/ssl/server-key.pem"
ETCD_TRUSTED_CA_FILE="/opt/etcd/ssl/ca.pem"
ETCD_CLIENT_CERT_AUTH="true"
ETCD_PEER_CERT_FILE="/opt/etcd/ssl/server.pem"
ETCD_PEER_KEY_FILE="/opt/etcd/ssl/server-key.pem"
ETCD_PEER_TRUSTED_CA_FILE="/opt/etcd/ssl/ca.pem"
ETCD_PEER_CLIENT_CERT_AUTH="true"

# 192.168.75.66
#[Member]
ETCD_NAME="etcd03"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.75.66:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.75.66:2379"

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.75.66:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.75.66:2379"
ETCD_INITIAL_CLUSTER="etcd01=https://192.168.75.64:2380,etcd02=https://192.168.75.65:2380,etcd03=https://192.168.75.66:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

#[Security]
ETCD_CERT_FILE="/opt/etcd/ssl/server.pem"
ETCD_KEY_FILE="/opt/etcd/ssl/server-key.pem"
ETCD_TRUSTED_CA_FILE="/opt/etcd/ssl/ca.pem"
ETCD_CLIENT_CERT_AUTH="true"
ETCD_PEER_CERT_FILE="/opt/etcd/ssl/server.pem"
ETCD_PEER_KEY_FILE="/opt/etcd/ssl/server-key.pem"
ETCD_PEER_TRUSTED_CA_FILE="/opt/etcd/ssl/ca.pem"
ETCD_PEER_CLIENT_CERT_AUTH="true"

# 都部署完成後，檢查etcd集羣狀態

/opt/etcd/bin/etcdctl --ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.75.64:2379,https://192.168.75.65:2379,https://192.168.75.66:2379" cluster-health


member a3174a13e9f88ee8 is healthy: got healthy result from https://192.168.75.65:2379
member d6f32b054860cf2b is healthy: got healthy result from https://192.168.75.64:2379
member e4ba0635cb718aa3 is healthy: got healthy result from https://192.168.75.66:2379
cluster is healthy

# 如果提示各類命令參數找不到，可使用/opt/etcd/bin/etcdctl --help命令查看後面的參數
# 不一樣的etcd版本後面跟的參數有可能不同

若是輸出上面信息，就說明集羣部署成功。若是有問題第一步先看日誌：/var/log/message 或 journalctl -u etcd

在Node安裝Docker

在node1和node2主機節點部署Docker

wget https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo -O /etc/yum.repos.d/docker-ce.repo
yum install -y yum-utils device-mapper-persistent-data lvm2
# K8S不支持最高版本的Docker，須要指定docker版本
yum -y install docker-ce-18.06.1.ce-3.el7

systemctl start docker && systemctl enable docker

這個操做步驟隨便一個主機上操做就行，目的是往etcd集羣中寫入數據
(使用etcdctl v3.4.3命令會獲得不一樣的返回結果)

# Falnnel要用etcd存儲自身一個子網信息，因此要保證能成功鏈接Etcd，寫入預約義子網段
/opt/etcd/bin/etcdctl --ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.75.64:2379,https://192.168.75.65:2379,https://192.168.75.66:2379" set /coreos.com/network/config  '{ "Network": "172.17.0.0/16", "Backend": {"Type": "vxlan"}}'

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

# 查看
/opt/etcd/bin/etcdctl --ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.75.64:2379,https://192.168.75.65:2379,https://192.168.75.66:2379" get /coreos.com/network/config  

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

# 刪除
/opt/etcd/bin/etcdctl --ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem --endpoints="https://192.168.75.64:2379,https://192.168.75.65:2379,https://192.168.75.66:2379" del /coreos.com/network/config

如下部署步驟在規劃的每一個node節點都操做

wget https://github.com/coreos/flannel/releases/download/v0.11.0/flannel-v0.11.0-linux-amd64.tar.gz
tar zxvf flannel-v0.11.0-linux-amd64.tar.gz
mkdir -p /opt/flannel/{bin,cfg}
cp flanneld mk-docker-opts.sh /opt/flannel/bin

使用腳本：

或者執行以下命令操做：flannel.sh
腳本用法：bash flannel.sh https://192.168.75.64:2379,https://192.168.75.65:2379,https://192.168.75.66:2379

# 配置Flannel

# cat /opt/flannel/cfg/flanneld
FLANNEL_OPTIONS="--etcd-endpoints=https://192.168.75.64:2379,https://192.168.75.65:2379,https://192.168.75.66:2379 -etcd-cafile=/opt/etcd/ssl/ca.pem -etcd-certfile=/opt/etcd/ssl/server.pem -etcd-keyfile=/opt/etcd/ssl/server-key.pem"

# 使用systemd管理Flannel

# cat /usr/lib/systemd/system/flanneld.service 
[Unit]
Description=Flanneld overlay address etcd agent
After=network-online.target network.target
Before=docker.service

[Service]
Type=notify
EnvironmentFile=/opt/flannel/cfg/flanneld
ExecStart=/opt/flannel/bin/flanneld --ip-masq $FLANNEL_OPTIONS
ExecStartPost=/opt/flannel/bin/mk-docker-opts.sh -k DOCKER_NETWORK_OPTIONS -d /run/flannel/subnet.env
Restart=on-failure

[Install]
WantedBy=multi-user.target

# 修改docker.service文件，結果以下：

# 配置Docker啓動指定子網段

# cat /usr/lib/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network-online.target firewalld.service
Wants=network-online.target

[Service]
Type=notify
EnvironmentFile=/run/flannel/subnet.env
ExecStart=/usr/bin/dockerd $DOCKER_NETWORK_OPTIONS
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

# 重啓flannel和docker

systemctl daemon-reload
systemctl start flanneld
systemctl enable flanneld

systemctl restart docker

# 檢查是否生效

# 確保docker0與flannel.1在同一網段

# ps -ef | grep docker
root       6879      1  0 14:14 ?        00:00:01 /usr/bin/dockerd --bip=172.17.69.1/24 --ip-masq=false --mtu=1450

# ip addr
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:77:67:ce:78 brd ff:ff:ff:ff:ff:ff
    inet 172.17.69.1/24 brd 172.17.69.255 scope global docker0
       valid_lft forever preferred_lft forever
4: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default 
    link/ether 52:96:0d:2d:ab:08 brd ff:ff:ff:ff:ff:ff
    inet 172.17.69.0/32 scope global flannel.1
       valid_lft forever preferred_lft forever
    inet6 fe80::5096:dff:fe2d:ab08/64 scope link 
       valid_lft forever preferred_lft forever

測試不一樣節點互通：

節點到容器
容器到節點
容器到容器

# node1節點ping本機docker ip
# ping -c 3 172.17.69.1
PING 172.17.69.1 (172.17.69.1) 56(84) bytes of data.
64 bytes from 172.17.69.1: icmp_seq=1 ttl=64 time=0.055 ms
64 bytes from 172.17.69.1: icmp_seq=2 ttl=64 time=0.030 ms
64 bytes from 172.17.69.1: icmp_seq=3 ttl=64 time=0.034 ms

--- 172.17.69.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.030/0.039/0.055/0.013 ms

# docker內容器ping node1本機ip
# 拉取一個最簡單的鏡像busybox
# docker run -it busybox 
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
0f8c40e1270f: Pull complete 
Digest: sha256:1303dbf110c57f3edf68d9f5a16c082ec06c4cf7604831669faf2c712260b5a0
Status: Downloaded newer image for busybox:latest
/ # ip addr # 查看172.17.69.2容器使用的ip
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue 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
5: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1450 qdisc noqueue 
    link/ether 02:42:ac:11:45:02 brd ff:ff:ff:ff:ff:ff
    inet 172.17.69.2/24 brd 172.17.69.255 scope global eth0
       valid_lft forever preferred_lft forever
/ # ping 192.168.75.65 -c 3 # ping 本機ip
PING 192.168.75.65 (192.168.75.65): 56 data bytes
64 bytes from 192.168.75.65: seq=0 ttl=64 time=0.168 ms
64 bytes from 192.168.75.65: seq=1 ttl=64 time=0.056 ms
64 bytes from 192.168.75.65: seq=2 ttl=64 time=0.063 ms

--- 192.168.75.65 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.056/0.095/0.168 ms
/ # ping -c 3 192.168.75.66 # ping node2節點的ip
PING 192.168.75.66 (192.168.75.66): 56 data bytes
64 bytes from 192.168.75.66: seq=0 ttl=63 time=0.609 ms
64 bytes from 192.168.75.66: seq=1 ttl=63 time=0.434 ms
64 bytes from 192.168.75.66: seq=2 ttl=63 time=0.315 ms

--- 192.168.75.66 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.315/0.452/0.609 ms
/ #

在Master節點部署組件

在部署Kubernetes以前必定要確保etcd、flannel、docker是正常工做的，不然先解決問題再繼續.

使用腳本：k8s-cert.sh

或者使用以下命令操做生成證書

# 生成證書

# 建立CA證書
# cat ca-config.json
{
  "signing": {
    "default": {
      "expiry": "87600h"
    },
    "profiles": {
      "kubernetes": {
         "expiry": "87600h",
         "usages": [
            "signing",
            "key encipherment",
            "server auth",
            "client auth"
        ]
      }
    }
  }
}

# cat ca-csr.json
{
    "CN": "kubernetes",
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "Beijing",
            "ST": "Beijing",
            "O": "k8s",
            "OU": "System"
        }
    ]
}

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

# 生成apiserver證書

# cat server-csr.json
{
    "CN": "kubernetes",
    "hosts": [
      "10.0.0.1",
      "127.0.0.1",
      "192.168.75.64",
      "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"
        }
    ]
}

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

# 生成kube-proxy證書

# cat kube-proxy-csr.json
{
  "CN": "system:kube-proxy",
  "hosts": [],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "L": "BeiJing",
      "ST": "BeiJing",
      "O": "k8s",
      "OU": "System"
    }
  ]
}

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

# 最終生成如下證書文件

# ls *.pem
ca-key.pem  ca.pem  kube-proxy-key.pem  kube-proxy.pem  server-key.pem  server.pem

部署apiserver組件

# 下載二進制包：https://github.com/kubernetes/kubernetes/releases
# 下載這個包（kubernetes-server-linux-amd64.tar.gz）就夠了，包含了所需的全部組件。

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

# 建立token文件

cat /opt/kubernetes/cfg/token.csv
674c457d4dcf2eefe4920d7dbb6b0ddc,kubelet-bootstrap,10001,"system:kubelet-bootstrap"

# 第一列：隨機字符串，本身可生成
# 第二列：用戶名
# 第三列：UID
# 第四列：用戶組

# 建立apiserver配置文件
# 配置好前面生成的證書，確保能鏈接etcd
cat /opt/kubernetes/cfg/kube-apiserver
KUBE_APISERVER_OPTS="--logtostderr=true \
--v=4 \
--etcd-servers=https://192.168.75.64:2379,https://192.168.75.65:2379,https://192.168.75.66:2379 \
--bind-address=192.168.75.64 \
--secure-port=6443 \
--advertise-address=192.168.75.64 \
--allow-privileged=true \
--service-cluster-ip-range=10.0.0.0/24 \
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota,NodeRestriction \
--authorization-mode=RBAC,Node \
--enable-bootstrap-token-auth \
--token-auth-file=/opt/kubernetes/cfg/token.csv \
--service-node-port-range=30000-50000 \
--tls-cert-file=/opt/kubernetes/ssl/server.pem  \
--tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \
--client-ca-file=/opt/kubernetes/ssl/ca.pem \
--service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \
--etcd-cafile=/opt/etcd/ssl/ca.pem \
--etcd-certfile=/opt/etcd/ssl/server.pem \
--etcd-keyfile=/opt/etcd/ssl/server-key.pem"

參數說明：

logtostderr 啓用日誌
-v 日誌等級
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 token文件
service-node-port-range Service Node類型默認分配端口範圍

# systemd管理apiserver

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

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

[Install]
WantedBy=multi-user.target

# 啓動
systemctl daemon-reload
systemctl enable kube-apiserver
systemctl start kube-apiserver

部署scheduler組件

# 建立schduler配置文件

# cat /opt/kubernetes/cfg/kube-scheduler
KUBE_SCHEDULER_OPTS="--logtostderr=true \
--v=4 \
--master=127.0.0.1:8080 \
--leader-elect"

參數說明：

--master 鏈接本地apiserver
--leader-elect 當該組件啓動多個時，自動選舉（HA）

# systemd管理schduler組件
# cat /usr/lib/systemd/system/kube-scheduler.service
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes

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

[Install]
WantedBy=multi-user.target

# 啓動
systemctl daemon-reload
systemctl enable kube-scheduler
systemctl start kube-scheduler

部署controller-manager組件

# 建立controller-manager配置文件

# cat /opt/kubernetes/cfg/kube-controller-manager
KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=true \
--v=4 \
--master=127.0.0.1:8080 \
--leader-elect=true \
--address=127.0.0.1 \
--service-cluster-ip-range=10.0.0.0/24 \
--cluster-name=kubernetes \
--cluster-signing-cert-file=/opt/kubernetes/ssl/ca.pem \
--cluster-signing-key-file=/opt/kubernetes/ssl/ca-key.pem  \
--root-ca-file=/opt/kubernetes/ssl/ca.pem \
--service-account-private-key-file=/opt/kubernetes/ssl/ca-key.pem"

# systemd管理controller-manager組件

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

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

[Install]
WantedBy=multi-user.target


# 啓動
systemctl daemon-reload
systemctl enable kube-controller-manager
systemctl start kube-controller-manager

全部組件都已經啓動成功，經過kubectl工具查看當前集羣組件狀態:

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

# 如上輸出說明組件都正常

或者分別執行master目錄下的sh腳本文件，注意腳本執行時須要參數

在Node節點部署組件

Master apiserver啓用TLS認證後，Node節點kubelet組件想要加入集羣，必須使用CA簽發的有效證書才能與apiserver通訊，當Node節點不少時，簽署證書是一件很繁瑣的事情，所以有了TLS Bootstrapping機制，kubelet會以一個低權限用戶自動向apiserver申請證書，kubelet的證書由apiserver動態簽署。

# 將kubelet-bootstrap用戶綁定到系統集羣角色

/opt/kubernetes/bin/kubectl create clusterrolebinding kubelet-bootstrap --clusterrole=system:node-bootstrapper --user=kubelet-bootstrap

# 執行結果
clusterrolebinding.rbac.authorization.k8s.io/kubelet-bootstrap created

# 建立kubeconfig文件

# 在生成kubernetes證書的目錄下執行如下命令生成kubeconfig文件
# 建立kubelet bootstrapping kubeconfig 
cd /opt/k8s_2
# 執行以下兩個命令
BOOTSTRAP_TOKEN=674c457d4dcf2eefe4920d7dbb6b0ddc
KUBE_APISERVER="https://192.168.75.64:6443"

# 設置集羣參數
/opt/kubernetes/bin/kubectl config set-cluster kubernetes --certificate-authority=./ca.pem --embed-certs=true --server=${KUBE_APISERVER} --kubeconfig=bootstrap.kubeconfig
# 執行結果
Cluster "kubernetes" set.

# 設置客戶端認證參數
/opt/kubernetes/bin/kubectl config set-credentials kubelet-bootstrap --token=${BOOTSTRAP_TOKEN} --kubeconfig=bootstrap.kubeconfig
# 執行結果
User "kubelet-bootstrap" set.

# 設置上下文參數
/opt/kubernetes/bin/kubectl config set-context default --cluster=kubernetes --user=kubelet-bootstrap --kubeconfig=bootstrap.kubeconfig
# 執行結果
Context "default" created.

# 設置默認上下文
/opt/kubernetes/bin/kubectl config use-context default --kubeconfig=bootstrap.kubeconfig
# 執行結果
Switched to context "default".

# 建立kube-proxy kubeconfig文件
/opt/kubernetes/bin/kubectl config set-cluster kubernetes --certificate-authority=./ca.pem --embed-certs=true --server=${KUBE_APISERVER} --kubeconfig=kube-proxy.kubeconfig
# 執行結果
Cluster "kubernetes" set.

/opt/kubernetes/bin/kubectl config set-credentials kube-proxy --client-certificate=./kube-proxy.pem --client-key=./kube-proxy-key.pem --embed-certs=true --kubeconfig=kube-proxy.kubeconfig
# 執行結果
User "kube-proxy" set.

/opt/kubernetes/bin/kubectl config set-context default --cluster=kubernetes --user=kube-proxy --kubeconfig=kube-proxy.kubeconfig
# 執行結果
Context "default" created.

/opt/kubernetes/bin/kubectl config use-context default --kubeconfig=kube-proxy.kubeconfig
# 執行結果
Switched to context "default".

# ls
bootstrap.kubeconfig  kube-proxy.kubeconfig
# 將這兩個文件拷貝到Node節點/opt/kubernetes/cfg目錄下

部署kubelet組件

將前面下載的二進制包中的kubelet和kube-proxy拷貝到/opt/kubernetes/bin目錄下

cd /opt/k8s_2/kubernetes/server/bin/
cp kubelet kube-proxy /opt/kubernetes/bin/

# 建立kubelet配置文件
# cat /opt/kubernetes/cfg/kubelet
KUBELET_OPTS="--logtostderr=true \
--v=4 \
--hostname-override=192.168.75.65 \
--kubeconfig=/opt/kubernetes/cfg/kubelet.kubeconfig \
--bootstrap-kubeconfig=/opt/kubernetes/cfg/bootstrap.kubeconfig \
--config=/opt/kubernetes/cfg/kubelet.config \
--cert-dir=/opt/kubernetes/ssl \
--pod-infra-container-image=registry.cn-hangzhou.aliyuncs.com/google-containers/pause-amd64:3.0"


# 其中/opt/kubernetes/cfg/kubelet.config配置文件以下：
kind: KubeletConfiguration
apiVersion: kubelet.config.k8s.io/v1beta1
address: 192.168.75.65
port: 10250
readOnlyPort: 10255
cgroupDriver: cgroupfs
clusterDNS: ["10.0.0.2"]
clusterDomain: cluster.local.
failSwapOn: false
authentication:
  anonymous:
    enabled: true


# systemd管理kubelet組件
# cat /usr/lib/systemd/system/kubelet.service 
[Unit]
Description=Kubernetes Kubelet
After=docker.service
Requires=docker.service

[Service]
EnvironmentFile=/opt/kubernetes/cfg/kubelet
ExecStart=/opt/kubernetes/bin/kubelet $KUBELET_OPTS
Restart=on-failure
KillMode=process

[Install]
WantedBy=multi-user.target

# 啓動
systemctl daemon-reload
systemctl enable kubelet
systemctl start kubelet

參數說明：

--hostname-override 在集羣中顯示的主機名
--kubeconfig 指定kubeconfig文件位置，會自動生成
--bootstrap-kubeconfig 指定剛纔生成的bootstrap.kubeconfig文件
--cert-dir 頒發證書存放位置
--pod-infra-container-image 管理Pod網絡的鏡像

在Master審批Node加入集羣

# 啓動後還沒加入到集羣中，須要手動容許該節點才能夠。在Master節點查看請求籤名的Node：
[root@bogon cfg]# /opt/kubernetes/bin/kubectl get csr
NAME                                                   AGE   REQUESTOR           CONDITION
node-csr-5O5xP__kXZ1UaDABvbe9u90WrV1EMwEYRYYeFLtO-7w   48s   kubelet-bootstrap   Pending

[root@bogon cfg]# /opt/kubernetes/bin/kubectl certificate approve node-csr-5O5xP__kXZ1UaDABvbe9u90WrV1EMwEYRYYeFLtO-7w
certificatesigningrequest.certificates.k8s.io/node-csr-5O5xP__kXZ1UaDABvbe9u90WrV1EMwEYRYYeFLtO-7w approved

[root@bogon cfg]# /opt/kubernetes/bin/kubectl get node
NAME            STATUS   ROLES    AGE   VERSION
192.168.75.65   Ready    <none>   12s   v1.12.1
[root@bogon cfg]#

部署kube-proxy組件

# 建立kube-proxy配置文件
# cat /opt/kubernetes/cfg/kube-proxy
KUBE_PROXY_OPTS="--logtostderr=true \
--v=4 \
--hostname-override=192.168.75.65 \
--cluster-cidr=10.0.0.0/24 \
--kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig"

# systemd管理kube-proxy組件
# cat /usr/lib/systemd/system/kube-proxy.service
[Unit]
Description=Kubernetes Proxy
After=network.target

[Service]
EnvironmentFile=-/opt/kubernetes/cfg/kube-proxy
ExecStart=/opt/kubernetes/bin/kube-proxy $KUBE_PROXY_OPTS
Restart=on-failure

[Install]
WantedBy=multi-user.target


# 啓動
systemctl daemon-reload
systemctl enable kube-proxy
systemctl start kube-proxy

Node2部署方式同樣
須要注意的是配置文件中的IP地址須要換成當前使用的

查看集羣狀態

# 在master主機上查看
/opt/kubernetes/bin/kubectl get node
NAME            STATUS   ROLES    AGE     VERSION
192.168.75.65   Ready    <none>   14m     v1.12.1
192.168.75.66   Ready    <none>   2m54s   v1.12.1

# 在node主機上查看會出現這樣的結果：The connection to the server localhost:8080 was refused - did you specify the right host or port?

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

運行一個測試示例

# 建立一個Nginx Web，測試集羣是否正常工做
/opt/kubernetes/bin/kubectl run nginx --image=nginx --replicas=3
# 執行結果
kubectl run --generator=deployment/apps.v1beta1 is DEPRECATED and will be removed in a future version. Use kubectl create instead.
deployment.apps/nginx created


/opt/kubernetes/bin/kubectl expose deployment nginx --port=88 --target-port=80 --type=NodePort
# 執行結果
service/nginx exposed

# 查看Pod，Service
/opt/kubernetes/bin/kubectl get pods
# 執行結果
NAME                    READY   STATUS    RESTARTS   AGE
nginx-dbddb74b8-4bd8v   1/1     Running   0          90s
nginx-dbddb74b8-5kjns   1/1     Running   0          90s
nginx-dbddb74b8-tbzhl   1/1     Running   0          90s

/opt/kubernetes/bin/kubectl get svc
# 執行結果
NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)        AGE
kubernetes   ClusterIP   10.0.0.1     <none>        443/TCP        100m
nginx        NodePort    10.0.0.116   <none>        88:37027/TCP   66s

# 訪問集羣中部署的Nginx，打開瀏覽器輸入：http://192.168.75.65:37027 或者http://192.168.75.66:37027

注意事項

flannel v0.11版本不支持etcd v3.4.3版本，支持etcd v3.3.10版本

由於etcd分v2和v3倆版本，不一樣版本使用的命令參數不一樣，獲得的結果也不一樣

若flannel v0.11使用etcd v3.4.3版本，則(Falnnel要用etcd存儲自身一個子網信息，因此要保證能成功鏈接Etcd，寫入預約義子網段)使用的命令會有變化，而後結果是能夠寫進去的。可是在啓動flannel的時候，會報錯：Couldn't fetch network config: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint.

這就是使用flannel版本跟etcd版本不支持的結果