小白學k8s--(1)二進位制部署k8s

阿新 • • 發佈：2020-11-18

二進位制部署k8s

二進位制部署k8s

前言

開始學習k8s吧，作為小白，先從手動搭建開始吧，然後在慢慢了解每個元件，本文經嘗試能夠成功部署成功。，本次嘗試是看了阿良老師的視訊，並且嘗試了很多次，才成功的。阿良老師的部落格地址，在下文有連結。

準備工作

關閉防火牆

關閉服務，並設為開機不自啟

$ sudo systemctl stop firewalld
$ sudo systemctl disable firewalld

清空防火牆規則

$ sudo iptables -F && sudo iptables -X && sudo iptables -F -t nat && sudo iptables -X -t nat
$ sudo iptables -P FORWARD ACCEPT

關閉 swap 分割槽

如果開啟了 swap 分割槽，kubelet 會啟動失敗(可以通過將引數 --fail-swap-on 設定為false 來忽略 swap on)，故需要在每臺機器上關閉 swap 分割槽：

$ sudo swapoff -a

為了防止開機自動掛載 swap 分割槽，可以註釋 /etc/fstab 中相應的條目：

$ sudo sed -i '/ swap / s/^\(.*\)$/#\1/g' /etc/fstab

關閉 SELinux

關閉 SELinux，否則後續 K8S 掛載目錄時可能報錯 Permission denied ：

$ sudo setenforce 0

修改配置檔案，永久生效；

$ grep SELINUX /etc/selinux/config

SELINUX=disabled

更新系統時間

1、調整系統 TimeZone

$ sudo timedatectl set-timezone Asia/Shanghai

2、將當前的 UTC 時間寫入硬體時鐘

$ sudo timedatectl set-local-rtc 0

3、重啟依賴於系統時間的服務

$ sudo systemctl restart rsyslog
$ sudo systemctl restart crond

4、更新時間

$ yum -y install ntpdate
$ sudo ntpdate cn.pool.ntp.org

祕鑰免密碼

$ ssh-copy-id [email protected]

設定主機名稱

192.168.56.201 kube-master
192.168.56.202 kube-node1
192.168.56.203 kube-node2

設定永久主機名稱，然後重新登入

$ sudo hostnamectl set-hostname kube-master
$ sudo hostnamectl set-hostname kube-node1
$ sudo hostnamectl set-hostname kube-node2

修改 /etc/hostname 檔案，新增主機名和 IP 的對應關係：

$ vim /etc/hosts

192.168.56.201 kube-master
192.168.56.202 kube-node1
192.168.56.203 kube-node2

伺服器角色

角色	ip	元件
kube-master	192.168.56.201	kube-apiserver，kube-controller-manager，kube-scheduler，etcd
kube-node1	192.168.56.202	kubelet，kube-proxy，docker，flannel，etcd
kube-node2	192.168.56.203	kubelet，kube-proxy，docker，flannel，etcd

安裝etcd

叢集中每臺機器都需要安裝，先在一臺節點安裝配置，之後把配置檔案scp到其他機器就行了

建立證書

使用cfssl來生成自簽證書

安裝

wget工具安裝yum -y install wget

$ 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

生成證書

證書一樣，保證叢集中使用的證書一致，在其中一臺機器中生成需要的證書，然後scp到其他的機器中

建立需要的檔案

建立資料夾/opt/etcd/ssl，etcd的證書檔案都放到這個資料夾中

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

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

$ vi server-csr.json
{
    "CN": "etcd",
    "hosts": [
    "192.168.56.201",
    "192.168.56.202",
    "192.168.56.203"
    ],
    "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

部署Etcd

$ wget https://github.com/etcd-io/etcd/releases/download/v3.2.12/etcd-v3.2.12-linux-amd64.tar.gz

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

建立配置檔案

$ vi /opt/etcd/cfg/etcd   
#[Member]
ETCD_NAME="etcd01"
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="https://192.168.56.201:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.56.201:2379"

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

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

$ vi /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 \
--name=${ETCD_NAME} \
--data-dir=${ETCD_DATA_DIR} \
--listen-peer-urls=${ETCD_LISTEN_PEER_URLS} \
--listen-client-urls=${ETCD_LISTEN_CLIENT_URLS},http://127.0.0.1:2379 \
--advertise-client-urls=${ETCD_ADVERTISE_CLIENT_URLS} \
--initial-advertise-peer-urls=${ETCD_INITIAL_ADVERTISE_PEER_URLS} \
--initial-cluster=${ETCD_INITIAL_CLUSTER} \
--initial-cluster-token=${ETCD_INITIAL_CLUSTER_TOKEN} \
--initial-cluster-state=new \
--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
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target

啟動

$ systemctl start etcd
$ systemctl enable etcd

只安裝了一臺機器，etcd是啟動不起來的，我們需要把其他機器的都安裝下

只需要把上面新增的檔案，scp到目標機器，然後修改下ip即可

檢視狀態

$ journalctl -u 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.56.201:2379,https://192.168.56.202:2379,https://192.168.56.203:2379" \
   cluster-health

  member 8c78d744f172cba9 is healthy: got healthy result from https://192.168.56.202:2379
  member bdc976e03235ad9b is healthy: got healthy result from https://192.168.56.201:2379
  member c6274de5e02a53ad is healthy: got healthy result from https://192.168.56.203:2379
  cluster is healthy

在Node安裝Docker

在node的每臺機器中安裝

$ yum install -y yum-utils device-mapper-persistent-data lvm2
$ yum-config-manager \
    --add-repo \
    https://download.docker.com/linux/centos/docker-ce.repo
$ yum install docker-ce -y
$ curl -sSL https://get.daocloud.io/daotools/set_mirror.sh | sh -s http://bc437cce.m.daocloud.io
$ systemctl start docker
$ systemctl enable docker

Flannel網路

Flannel是部署在node中的，每個node都需要安裝，master節點無需安裝

配置子網

$ /opt/etcd/bin/etcdctl \
--ca-file=/opt/etcd/ssl/ca.pem --cert-file=/opt/etcd/ssl/server.pem --key-file=/opt/etcd/ssl/server-key.pem \
--endpoints="https://192.168.56.201:2379,https://192.168.56.202:2379,https://192.168.56.203:2379" \
set /coreos.com/network/config  '{ "Network": "172.17.0.0/16", "Backend": {"Type": "vxlan"}}'

在一個node中安裝，然後把配置的檔案scp到其他node中

$ wget https://github.com/coreos/flannel/releases/download/v0.9.1/flannel-v0.9.1-linux-amd64.tar.gz
$ tar zxvf flannel-v0.9.1-linux-amd64.tar.gz
$ mv flanneld mk-docker-opts.sh /opt/kubernetes/bin

配置Flannel

$ vi /opt/kubernetes/cfg/flanneld
FLANNEL_OPTIONS="--etcd-endpoints=https://192.168.56.201:2379,https://192.168.56.202:2379,https://192.168.56.203: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

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

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

[Install]
WantedBy=multi-user.target

配置Docker啟動指定子網段

$ vi /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的配置

EnvironmentFile=/run/flannel/subnet.env
ExecStart=/usr/bin/dockerd $DOCKER_NETWORK_OPTIONS

重啟flannel和docker：

# systemctl daemon-reload
# systemctl start flanneld
# systemctl enable flanneld
# systemctl restart docker

檢查是否生效

$ ps -ef |grep docker
root      2859     1  0 18:13 ?        00:00:05 /usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --init-path=/usr/libexec/docker/docker-init-current --seccomp-profile=/etc/docker/seccomp.json --selinux-enabled --log-driver=journald --signature-verification=false --storage-driver overlay2 --bip=172.17.96.1/24 --ip-masq=false --mtu=1450
root      2865  2859  0 18:13 ?        00:00:02 /usr/bin/docker-containerd-current -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --shim docker-containerd-shim --runtime docker-runc --runtime-args --systemd-cgroup=true
root      5799  1753  0 18:49 pts/0    00:00:00 grep --color=auto docker

$ 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
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:73:3f:bf brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.7/24 brd 10.0.2.255 scope global noprefixroute dynamic enp0s3
       valid_lft 416sec preferred_lft 416sec
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:7b:1e:59 brd ff:ff:ff:ff:ff:ff
    inet 192.168.56.203/24 brd 192.168.56.255 scope global noprefixroute enp0s8
       valid_lft forever preferred_lft forever
4: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default 
    link/ether c6:65:64:77:fd:04 brd ff:ff:ff:ff:ff:ff
    inet 172.17.96.0/32 scope global flannel.1
       valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:9a:42:ae:5b brd ff:ff:ff:ff:ff:ff
    inet 172.17.96.1/24 scope global docker0
       valid_lft forever preferred_lft forever

測試不同節點互通，在當前節點訪問另一個Node節點flannel網路

$ ping 172.17.72.0
PING 172.17.72.0 (172.17.72.0) 56(84) bytes of data.
64 bytes from 172.17.72.0: icmp_seq=1 ttl=64 time=1.25 ms
64 bytes from 172.17.72.0: icmp_seq=2 ttl=64 time=0.507 ms
64 bytes from 172.17.72.0: icmp_seq=3 ttl=64 time=1.17 ms
64 bytes from 172.17.72.0: icmp_seq=4 ttl=64 time=1.84 ms
64 bytes from 172.17.72.0: icmp_seq=5 ttl=64 time=0.426 ms

本人在部署的時候，選了最高版本的flannel，但是發現部署一致不成功，google了發現，需要找和etcd版本符合的flannel版本進行部署。

master節點部署元件

master節點需要部署apiserver，不過前面部署的etcd,docker,flannel需要保證正常執行

生成證書

將證書統一放在/opt/kubernetes/ssl/進行管理

建立ca證書

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

$ vi 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證書

$ vi server-csr.json
{
    "CN": "kubernetes",
    "hosts": [
      "10.0.0.1",
      "127.0.0.1",
      "192.168.56.201",
      "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證書

$ vi 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，我下載的是v1.18.12

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

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

第一列：隨機字串，自己可生成
第二列：使用者名稱
第三列：UID
第四列：使用者組

建立apiserver配置檔案：

$ vi /opt/kubernetes/cfg/kube-apiserver 

KUBE_APISERVER_OPTS="--logtostderr=true \
--v=4 \
--etcd-servers=https://192.168.56.201:2379,https://192.168.56.202:2379,https://192.168.56.203:2379 \
--bind-address=192.168.56.201 \
--secure-port=6443 \
--advertise-address=192.168.56.201 \
--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"

配置好前面生成的證書，確保能連線etcd。

引數說明：

--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：

$ vi /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 restart kube-apiserver

部署scheduler元件

建立schduler配置檔案

$ vi /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元件

$ vi /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 restart kube-scheduler

部署controller-manager元件

建立controller-manager配置檔案

$ vi /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元件

$ vi /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 restart kube-controller-manager

安裝完成檢視當前的元件的狀態

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

出現Healthy表示元件都正常

在Node節點部署元件

Master apiserver啟用TLS認證後，Node節點kubelet元件想要加入叢集，必須使用CA簽發的有效證書才能與apiserver通訊，當Node節點很多時，簽署證書是一件很繁瑣的事情，因此有了TLS Bootstrapping機制，kubelet會以一個低許可權使用者自動向apiserver申請證書，kubelet的證書由apiserver動態簽署。

認證大致工作流程如圖所示：

將master節點將kubelet-bootstrap使用者繫結到系統叢集角色

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

建立kubeconfig檔案

在生成kubernetes證書的目錄下執行以下命令生成kubeconfig檔案,在master節點生成bootstrap.kubeconfig kube-proxy.kubeconfig然後scp到node節點

可以藉助一個sh來實現,目錄/opt/kubernetes/cfg

$ vi kubeconfig.sh 

# 建立 TLS Bootstrapping Token
#BOOTSTRAP_TOKEN=$(head -c 16 /dev/urandom | od -An -t x | tr -d ' ')
BOOTSTRAP_TOKEN=674c457d4dcf2eefe4920d7dbb6b0ddc

cat > token.csv <<EOF
${BOOTSTRAP_TOKEN},kubelet-bootstrap,10001,"system:kubelet-bootstrap"
EOF

#----------------------

APISERVER=192.168.56.201
SSL_DIR=/opt/kubernetes/ssl

# 建立kubelet bootstrapping kubeconfig 
export KUBE_APISERVER="https://$APISERVER:6443"

# 設定叢集引數
kubectl config set-cluster kubernetes \
  --certificate-authority=$SSL_DIR/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=bootstrap.kubeconfig

# 設定客戶端認證引數
kubectl config set-credentials kubelet-bootstrap \
  --token=${BOOTSTRAP_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

#----------------------

# 建立kube-proxy kubeconfig檔案

kubectl config set-cluster kubernetes \
  --certificate-authority=$SSL_DIR/ca.pem \
  --embed-certs=true \
  --server=${KUBE_APISERVER} \
  --kubeconfig=kube-proxy.kubeconfig

kubectl config set-credentials kube-proxy \
  --client-certificate=$SSL_DIR/kube-proxy.pem \
  --client-key=$SSL_DIR/kube-proxy-key.pem \
  --embed-certs=true \
  --kubeconfig=kube-proxy.kubeconfig

kubectl config set-context default \
  --cluster=kubernetes \
  --user=kube-proxy \
  --kubeconfig=kube-proxy.kubeconfig

kubectl config use-context default --kubeconfig=kube-proxy.kubeconfig

其中BOOTSTRAP_TOKEN就是上文我們設定的/opt/kubernetes/cfg/token.csv中的token

生成

$ bash kubeconfig.sh

$ ls
bootstrap.kubeconfig  kube-proxy.kubeconfig

部署kubelet元件

需要在每個node節點部署

把前面在master節點下載的kubernetes-server-linux-amd64.tar.gz中的二進位制包中的kubelet和kube-proxy拷貝到/opt/kubernetes/bin目錄下。

建立kubelet配置檔案

$ vi /opt/kubernetes/cfg/kubelet
KUBELET_OPTS="--logtostderr=true \
--v=4 \
--hostname-override=192.168.56.202 \
--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"

引數說明

--hostname-override 在叢集中顯示的主機名
--kubeconfig 指定kubeconfig檔案位置，會自動生成
--bootstrap-kubeconfig 指定剛才生成的bootstrap.kubeconfig檔案
--cert-dir 頒發證書存放位置
--pod-infra-container-image 管理Pod網路的映象

kubelet.config的配製

$ vi /opt/kubernetes/cfg/kubelet.config

kind: KubeletConfiguration
apiVersion: kubelet.config.k8s.io/v1beta1
address: 192.168.56.202
port: 10250
readOnlyPort: 10255
cgroupDriver: cgroupfs
clusterDNS: ["10.0.0.2"]
clusterDomain: cluster.local.
failSwapOn: false
authentication:
  anonymous:
    enabled: true

systemd管理kubelet元件

$ vi /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 restart kubelet

在Master審批Node加入叢集

master節點會收到node的驗證請求，我們需要在master節點approve下

$ kubectl get csr
$ kubectl certificate approve XXXXID
$ kubectl get node

檢視

$ kubectl get csr
NAME                                                   AGE       REQUESTOR           CONDITION
node-csr-gE0iy6gY71RqRlC1ZhGGnvLwKBjLGmnTNmEoFj51yU4   26s       kubelet-bootstrap   Pending
node-csr-jFvVR_RBv-swHScxKEf_yDt_J72twIBTeslF8Bv18LQ   24s       kubelet-bootstrap   Pending

Pending狀態的需要approve

$ kubectl certificate approve node-csr-gE0iy6gY71RqRlC1ZhGGnvLwKBjLGmnTNmEoFj51yU4

部署kube-proxy元件

每個node節點都需要執行

建立kube-proxy配置檔案

$ vi /opt/kubernetes/cfg/kube-proxy
KUBE_PROXY_OPTS="--logtostderr=true \
--v=4 \
--hostname-override=192.168.56.202 \
--cluster-cidr=10.0.0.0/24 \
--kubeconfig=/opt/kubernetes/cfg/kube-proxy.kubeconfig"

systemd管理kube-proxy元件

$ vi /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 restart kube-proxy

檢視叢集狀態

$ kubectl get node
NAME             STATUS   ROLES    AGE    VERSION
192.168.56.202   Ready    <none>   18h    v1.18.12
192.168.56.203   Ready    <none>   171m   v1.18.12

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

測試

建立測試檔案

$ vi /opt/kubernetes/demo/nginx-ds.yml 

apiVersion: v1
kind: Service
metadata:
  name: nginx-ds
  labels:
    app: nginx-ds
spec:
  type: NodePort
  selector:
    app: nginx-ds
  ports:
  - name: http
    port: 80
    targetPort: 80
---

apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
kind: Deployment
metadata:
  name: nginx-ds
spec:
  selector:
    matchLabels:
      app: nginx-ds
  replicas: 3 # tells deployment to run 2 pods matching the template
  template:
    metadata:
      labels:
        app: nginx-ds
    spec:
      containers:
      - name: nginx
        image: nginx:1.14.2
        ports:
        - containerPort: 80

執行

$ kubectl apply -f nginx-ds.yml

結果

$  kubectl get pod
NAME                        READY   STATUS              RESTARTS   AGE
nginx-ds-76d6f5ffdd-2hds5   0/1     ContainerCreating   0          89s
nginx-ds-76d6f5ffdd-gv87x   0/1     ContainerCreating   0          16s
nginx-ds-76d6f5ffdd-m5dp5   0/1     ContainerCreating   0          89s

過一會就會自動建立成功

$  kubectl get pods -o wide|grep nginx-ds
nginx-ds-76d6f5ffdd-2hds5           1/1     Running   0          34m   172.17.21.4   192.168.56.203   <none>           <none>
nginx-ds-76d6f5ffdd-gv87x           1/1     Running   0          34m   172.17.46.4   192.168.56.202   <none>           <none>
nginx-ds-76d6f5ffdd-m5dp5           1/1     Running   0          34m   172.17.46.3   192.168.56.202   <none>           <none>

$  kubectl get svc |grep nginx-ds
nginx-ds     NodePort    10.0.0.112   <none>        80:41675/TCP   35m

$ curl 192.168.56.203:41675/

<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

已經可以訪問了

參考

【二進位制安裝部署kubernetes叢集---超詳細教程】https://www.cnblogs.com/along21/p/10044931.html
【etcd時間同步】https://bingohuang.com/etcd-operation-2/
【Kubernetes v1.12/v1.13 二進位制部署叢集（HTTPS+RBAC）】https://blog.51cto.com/lizhenliang/2325770

小白學k8s--(1)二進位制部署k8s

二進位制部署k8s

前言

準備工作

關閉防火牆

關閉 swap 分割槽

關閉 SELinux

更新系統時間

祕鑰免密碼

設定主機名稱

伺服器角色

安裝etcd

建立證書

生成證書

部署Etcd

在Node安裝Docker

Flannel網路

master節點部署元件

生成證書

配置apiserver元件

部署scheduler元件

部署controller-manager元件

在Node節點部署元件

建立kubeconfig檔案

部署kubelet元件

部署kube-proxy元件

檢視叢集狀態

測試

參考

相關推薦