二進制搭建kubernetes-1.18.6單master集群

本文轉載自查看原文 2020-10-06 13:34 469 k8s

master組件

kube-apiserver

kubernetes API集群的同一入口，各組件協調者，以RESTful API提供接口服務，所有對象資源的增刪改查和監聽操作都交給APIserver處理再提交給Etcd存儲

kube-controller-manager

處理集群中常規后台任務，一個資源對應一個控制器，而ControllerManager就是負責管理這些控制器的

kube-scheduler

根據調度算法為新創建的POdxuanz yig Node節點，可以在任意部署，可以部署在同一個節點上，也可以部署在不同節點上

etcd

分布式鍵值存儲系統，用於報銷集群狀態數據，比如Pod、service等對象信息

Node組件

kubelet

kubelet是master在node節點上的agent，管理本機運行容器的生命周期，比如創建容器、Pod掛載數據卷、下載secret、獲取容器和節點狀態等工作，kubelet將每個Pod轉成一組容器。

kube-proxy

在Node節點上實現Pod網絡代理，維護網絡規則和四層負載均衡工作

docker或rocket

容器引擎，運行容器

服務器硬件配置推薦

實驗環境	K8s master/node	2核2G+
測試環境	K8s-master	CPU	2核
		內存	4G
		硬盤	20G
	K8s-node	CPU	4核
		內存	8G
		硬盤	20G
生產環境	K8s-master	CPU	8核
		內存	16G
		硬盤	100G
	K8s-node	CPU	16核
		內存	64G
		硬盤	500G

當然資源越多肯定是越好的，也要看實際需求來衡量需求的資源

單Master服務器規划

角色	IP	組件
k8s-master-1	192.168.10.160	kube-apiserver，kube-controller-manager，kube-scheduler，etcd
k8s-node-1	192.168.10.161	kubelet，kube-proxy，docker etcd
k8s-node-2	192.168.10.162	kubelet，kube-proxy，docker，etcd

Etcd 是一個分布式鍵值存儲系統，Kubernetes使用Etcd進行數據存儲，所以先准備一個Etcd數據庫，為解決Etcd單點故障，應采用集群方式部署，

這里使用3台組建集群，可容忍1台機器故障，當然，你也可以使用5台組建集群，可容忍2台機器故障。

節點名稱	IP
etcd-1	192.168.10.160
etcd-2	192.168.10.161
etcd-3	192.168.10.162

注：為了節省機器，這里與K8s節點機器復用。也可以獨立於k8s集群之外部署，只要apiserver能連接到就行。

系統環境

[root@localhost ~]# cat /etc/redhat-release
CentOS Linux release 7.8.2003 (Core)
[root@localhost ~]# uname -a
Linux localhost 3.10.0-1127.18.2.el7.x86_64 #1 SMP Sun Jul 26 15:27:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost ~]#

一、基礎優化

1、時間同步

echo "#time sync by fage at 2019-7-22" >>/var/spool/cron/root 
echo "*/5 * * * *  /usr/sbin/ntpdate ntp1.aliyun.com >/dev/null 2>&1" >>/var/spool/cron/root  
systemctl restart crond.service

2、關閉防火牆和selinux

systemctl stop firewalld 
systemctl disable firewalld 
setenforce 0 
sed -i s#SELINUX=enforcing#SELINUX=disable#g /etc/selinux/config

3、更改主機名

master

hostname k8s-master-1
echo "k8s-master-1" >/etc/hostname

node

hostname k8s-node-1
echo " k8s-node-1" >/etc/hostname

hostname k8s-node-2
echo " k8s-node-2" >/etc/hostname

4、更改hosts文件

cat >/etc/hosts <<EOF
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.10.160 k8s-master-1
192.168.10.161 k8s-node-1
192.168.10.162 k8s-node-2
EOF

5、節點node要禁用swap設備不禁用要配置聲明

swapoff -a
sed -i "s@/dev/mapper/centos-swap swap@#/dev/mapper/centos-swap swap@g" /etc/fstab

6、將橋接的IPv4流量傳遞到iptables的鏈

cat > /etc/sysctl.d/k8s.conf << EOF
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system  # 生效配置

二、部署Etcd集群

2.1 准備cfssl證書生成工具

找任意一台服務器操作，這里用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證書

2.2.1. 自簽證書頒發機構（CA）

創建工作目錄

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 - && ls *pem

2.2.2. 使用自簽CA簽發Etcd HTTPS證書

創建證書申請文件

cat > server-csr.json << EOF
{
    "CN": "etcd",
    "hosts": [
    "192.168.10.160",
    "192.168.10.161",
    "192.168.10.162",
    "192.168.10.163"
    ],
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "BeiJing",
            "ST": "BeiJing"
        }
    ]
}
EOF

注：上述文件hosts字段中IP為所有etcd節點的集群內部通信IP，一個都不能少！為了方便后期擴容可以多寫幾個預留的IP。

生成證書

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

ls server*pem

2.2.3、部署Etcd集群

以下在master上操作，為簡化操作，待會將master生成的所有文件拷貝到節點2和節點3.

1. 創建工作目錄並解壓二進制包

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

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/

2. 創建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.10.160:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.10.160:2379"
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.10.160:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.10.160:2379"
ETCD_INITIAL_CLUSTER="etcd-1=https://192.168.10.160:2380,etcd-2=https://192.168.10.161:2380,etcd-3=https://192.168.10.162: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表示加入已有集群

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

4. 拷貝剛才生成的證書

master操作：把剛才生成的證書拷貝到配置文件中的路徑　　

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

5. 啟動並設置開機啟動

systemctl daemon-reload && systemctl start etcd && systemctl enable etcd

6. 將上面節點1所有生成的文件拷貝到節點2和節點3

scp -r /opt/etcd/ root@192.168.10.161:/opt/
scp /usr/lib/systemd/system/etcd.service root@192.168.10.161:/usr/lib/systemd/system/
scp -r /opt/etcd/ root@192.168.10.162:/opt/
scp /usr/lib/systemd/system/etcd.service root@192.168.10.162:/usr/lib/systemd/system/

然后在節點2和節點3分別修改etcd.conf配置文件中的節點名稱和當前

服務器IP：每台集群都要改成自身機器的名稱和地址和檢查一遍

vi /opt/etcd/cfg/etcd.conf
#[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.10.160:2380"   # 修改此處為當前服務器IP
ETCD_LISTEN_CLIENT_URLS="https://192.168.10.160:2379" # 修改此處為當前服務器IP

#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.10.160:2380" # 修改此處為當前服務器IP
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.10.160:2379" # 修改此處為當前服務器IP
ETCD_INITIAL_CLUSTER="etcd-1=https://192.168.10.160:2380,etcd-2=https://192.168.10.161:2380,etcd-3=https://192.168.10.162:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

在其他的全部節點上設置開機自啟動

systemctl daemon-reload && systemctl start etcd && systemctl enable etcd

7. 查看ETCD集群狀態

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.10.160:2379,https://192.168.10.161:2379,https://192.168.10.162:2379" endpoint health
#輸出的結果
https://192.168.10.162:2379 is healthy: successfully committed proposal: took = 13.108591ms
https://192.168.10.160:2379 is healthy: successfully committed proposal: took = 13.436323ms
https://192.168.10.161:2379 is healthy: successfully committed proposal: took = 15.027817ms

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

三、安裝Docker

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

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

1、解壓二進制包

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

2、systemd管理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、創建配置文件

registry-mirrors 阿里雲鏡像加速器

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

復制到其他節點機器上

cd /usr/bin/
scp -r /usr/lib/systemd/system/docker.service root@192.168.10.161:/usr/lib/systemd/system/
scp -r containerd containerd-shim docker dockerd docker-init  docker-proxy runc root@192.168.10.161:/usr/bin/
scp -r /etc/docker root@192.168.10.161:/etc/
cd /usr/bin/
scp -r /usr/lib/systemd/system/docker.service root@192.168.10.162:/usr/lib/systemd/system/
scp -r containerd containerd-shim docker dockerd docker-init  docker-proxy runc root@192.168.10.162:/usr/bin/
scp -r /etc/docker root@192.168.10.162:/etc/

4、其他節點啟動並設置開機啟動

systemctl daemon-reload && systemctl start docker &&systemctl enable docker

四、部署Master Node （全在master操作）　

4.1 生成kube-apiserver證書

1. 自簽證書頒發機構（CA）

cd /root/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 - && ls *pem

ca-key.pem  ca.pem

2. 使用自簽CA簽發kube-apiserver HTTPS證書

創建證書申請文件　　

cd /root/TLS/k8s
cat > server-csr.json << EOF
{
    "CN": "kubernetes",
    "hosts": [
      "10.0.0.1",
      "127.0.0.1",
      "192.168.10.160",
      "192.168.10.161",
      "192.168.10.162",
      "192.168.10.163",
      "192.168.10.164",
      "192.168.10.165",
      "192.168.10.166",
      "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

ls server*pem
server-key.pem  server.pem

4.2 從Github下載二進制文件

下載地址：

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.18.md#downloads-for-v1186

注：打開鏈接你會發現里面有很多包，下載一個server包就夠了，包含了Master和Worker Node二進制文件。

https://storage.googleapis.com/kubernetes-release/release/v1.18.6/kubernetes-server-linux-amd64.tar.gz

下載1.18.6版本的

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://192.168.10.160:2379,https://192.168.10.161:2379,https://192.168.10.162:2379 \\
--bind-address=192.168.10.160 \\
--secure-port=6443 \\
--advertise-address=192.168.10.160 \\
--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. 拷貝剛才生成的證書

把剛才生成的證書拷貝到配置文件中的路徑

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

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
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  && systemctl status 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
systemctl status 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
systemctl status kube-scheduler

4. 查看集群狀態

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

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

如上輸出說明Master節點組件運行正常。

五、部署Worker Node

下面還是在Master上操作，即同時作為Worker Node

5.1 創建工作目錄並拷貝二進制文件

在所有worker node創建工作目錄　　

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

從master節點拷貝

cd kubernetes/server/bin
cp kubelet kube-proxy /opt/kubernetes/bin   # 本地拷貝

scp -r kubelet kube-proxy root@192.168.10.161:/opt/kubernetes/bin/
scp -r kubelet kube-proxy root@192.168.10.162:/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://192.168.10.160: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

拷貝到配置文件路徑

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.1 批准kubelet證書申請並加入集群

查看kubelet證書請求

kubectl get csr
NAME                                                   AGE    SIGNERNAME                                    REQUESTOR           CONDITION
node-csr-uCEGPOIiDdlLODKts8J658HrFq9CZ--K6M4G7bjhk8A   6m3s   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Pending

批准申請　

kubectl certificate approve node-csr-uCEGPOIiDdlLODKts8J658HrFq9CZ--K6M4G7bjhk8A

查看節點

kubectl get node

注：由於網絡插件還沒有部署，節點會沒有准備就緒 NotReady

5.2 部署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 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

ls kube-proxy*pem
kube-proxy-key.pem  kube-proxy.pem

生成kubeconfig文件

KUBE_APISERVER="https://192.168.10.160: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
systemctl status kube-proxy

5.3 部署CNI網絡

先准備好CNI二進制文件：

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

解壓二進制包並移動到默認工作目錄

mkdir -p /opt/cni/bin
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#lizhenliang/flannel:v0.12.0-amd64#g" kube-flannel.yml

默認鏡像地址在國外無法訪問，修改為docker hub鏡像倉庫地址

kubectl apply -f kube-flannel.yml

kubectl get pods -n kube-system
NAME                          READY   STATUS    RESTARTS   AGE
kube-flannel-ds-amd64-2pc95   1/1     Running   0          72s

kubectl get node
NAME         STATUS   ROLES    AGE   VERSION
k8s-master   Ready    <none>   41m   v1.18.6

部署好網絡插件，Node准備就緒　　

5.4 授權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

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

5.5 新增加Worker Node，其他節點操作

1. 拷貝已部署好的Node相關文件到新節點

在master節點將Worker Node涉及文件拷貝到新節點192.168.10.161/162

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

2. 刪除kubelet證書和kubeconfig文件

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

注：這幾個文件是證書申請審批后自動生成的，每個Node不同，必須刪除重新生成。

3. 修改主機名

sed -i "s#k8s-master#k8s-node-1#g" /opt/kubernetes/cfg/kubelet.conf
sed -i "s#k8s-master#k8s-node-1#g" /opt/kubernetes/cfg/kube-proxy-config.yml
sed -i "s#k8s-master#k8s-node-2#g" /opt/kubernetes/cfg/kubelet.conf
sed -i "s#k8s-master#k8s-node-2#g" /opt/kubernetes/cfg/kube-proxy-config.yml

4. 啟動並設置開機啟動

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

5. 在Master上批准新所有Node kubelet證書申請

kubectl get csr
NAME                                                   AGE   SIGNERNAME                                    REQUESTOR           CONDITION
node-csr-4zTjsaVSrhuyhIGqsefxzVoZDCNKei-aE2jyTP81Uro   89s   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Pending

kubectl certificate approve node-csr-4zTjsaVSrhuyhIGqsefxzVoZDCNKei-aE2jyTP81Uro

6. 查看Node狀態

kubectl get node
NAME         STATUS     ROLES    AGE   VERSION
k8s-master   Ready      <none>   65m   v1.18.6
k8s-node1    Ready      <none>   12m   v1.18.6
k8s-node2    Ready      <none>   81s   v1.18.6

Node2（192.168.10.162 ）節點同上。記得修改主機名！

六、部署Dashboard和CoreDNS

6.1 部署Dashboard

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

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

vi 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
kubectl get pods,svc -n kubernetes-dashboard
NAME                                             READY   STATUS              RESTARTS   AGE
pod/dashboard-metrics-scraper-694557449d-z8gfb   1/1     Running             0          2m18s
pod/kubernetes-dashboard-9774cc786-q2gsx         1/1     Running		     0          2m19s

NAME                                TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)         AGE
service/dashboard-metrics-scraper   ClusterIP   10.0.0.141   <none>        8000/TCP        2m19s
service/kubernetes-dashboard        NodePort    10.0.0.239   <none>        443:30001/TCP   2m19s

訪問地址：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

使用輸出的token登錄Dashboard　　

6.2 部署CoreDNS

CoreDNS用於集群內部Service名稱解析

wget https://github.com/dsalamancaMS/CoreDNSforKube/blob/master/coredns.yaml

kubectl apply -f coredns.yaml
kubectl get pods -n kube-system 
NAME                          READY   STATUS    RESTARTS   AGE
coredns-5ffbfd976d-j6shb      1/1     Running   0          32s
kube-flannel-ds-amd64-2pc95   1/1     Running   0          38m
kube-flannel-ds-amd64-7qhdx   1/1     Running   0          15m
kube-flannel-ds-amd64-99cr8   1/1     Running   0          26m

DNS解析測試　　

kubectl run -it --rm dns-test --image=busybox:1.28.4 sh
If you don't see a command prompt, try pressing enter.

/ # nslookup kubernetes
Server:    10.0.0.2
Address 1: 10.0.0.2 kube-dns.kube-system.svc.cluster.local

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

至此，單Master集群部署完成

免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。

猜您在找 二進制搭建kubernetes多master集群【二、配置flannel網絡】二進制搭建kubernetes多master集群【一、使用TLS證書搭建etcd集群】二進制搭建kubernetes多master集群【三、配置k8s master及高可用】二進制搭建kubernetes多master集群【開篇、集群環境和功能介紹】二進制搭建kubernetes多master集群【四、配置k8s node】 Kubernetes 二進制部署-V1.18.6 Kubernetes二進制（單/多master）部署 kubernetes二進制部署k8s-master集群controller-manager服務unhealthy問題 2、二進制部署kubernetes集群（下篇） 1、二進制部署kubernetes集群（上篇）