二進制部署kubernetes——1.20.4

1赴魁、環(huán)境準備

操作系統(tǒng)：ecntos7.6
容器引擎：docker-ce-19
kubernetes：1.20.4

2、服務(wù)器整體規(guī)劃

k8s-master1 192.168.145.100 kube-apiserver空厌，kube-controller-manager庐船，kube-scheduler，kubelet嘲更，kube-proxy筐钟，docker
k8s-node1 192.168.145.101 kubelet，kube-proxy赋朦，docker
k8s-node2 192.168.145.102 kubelet篓冲，kube-proxy，docker
k8s-etcd-1 192.168.145.103 etcd
k8s-etcd-2 192.168.145.104 etcd
k8s-etcd-3 192.168.145.105 etcd

3宠哄、系統(tǒng)初始化配置

3.1壹将、關(guān)閉防火墻(所有節(jié)點)

systemctl stop firewalld 
systemctl disable firewalld

3.2、關(guān)閉selinux(所有節(jié)點)

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

3.3毛嫉、關(guān)閉swap(所有節(jié)點)

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

3.4诽俯、根據(jù)規(guī)劃設(shè)置主機名(所有節(jié)點)

hostnamectl set-hostname <hostname>

3.5、添加hosts(所有節(jié)點)

cat >> /etc/hosts << EOF 
192.168.145.100 k8s-master
192.168.145.101 k8s-node1
192.168.145.102 k8s-node2
192.168.145.103 k8s-etcd-1
192.168.145.104 k8s-etcd-2
192.168.145.105 k8s-etcd-3
EOF

3.6承粤、將IPv4流量傳遞到iptables的鏈(所有節(jié)點)

cat > /etc/sysctl.d/k8s.conf << EOF 
net.bridge.bridge-nf-call-ip6tables = 1 
net.bridge.bridge-nf-call-iptables = 1 
EOF

sysctl --system  # 生效

3.7暴区、時間同步(所有節(jié)點)

yum install ntpdate -y 
ntpdate time.windows.com

4、證書說明

在這里插入圖片描述

5密任、部署Etcd集群

Etcd 是一個分布式鍵值存儲系統(tǒng)颜启，Kubernetes使用Etcd進行數(shù)據(jù)存儲，所以先準備一個Etcd數(shù)據(jù)庫浪讳，為解決Etcd單點故障缰盏，應(yīng)采用集群方式部署,這里使用3臺組建集群，可容忍1臺機器故障.

5.1、準備cfssl證書生成工具

5.2口猜、在master節(jié)點操作

下載軟件包
mkdir /root/liu/cfssl && cd /root/liu/cfssl/
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

5.3负溪、生成Etcd證書

5.3.1、創(chuàng)建工作目錄

mkdir -p /root/liu/{etcd,k8s} && cd /root/liu/etcd

5.3.2济炎、自簽證書頒發(fā)機構(gòu)（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

生成證書：會生成ca.pem和ca-key.pem文件
cfssl gencert -initca ca-csr.json | cfssljson -bare ca -

5.3.3川抡、使用自簽CA簽發(fā)Etcd Https證書

創(chuàng)建證書請求文件
cat > server-csr.json << EOF
{
    "CN": "etcd",
    "hosts": [
    "192.168.145.103",
    "192.168.145.104",
    "192.168.145.105"
    ],
    "key": {
        "algo": "rsa",
        "size": 2048
    },
    "names": [
        {
            "C": "CN",
            "L": "BeiJing",
            "ST": "BeiJing"
        }
    ]
}
EOF
hosts字段中IP為所有etcd節(jié)點的集群內(nèi)部通信IP
生成證書，會生成server.pem和server-key.pem文件
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=www server-csr.json | cfssljson -bare server

5.4须尚、開始部署ETCD集群

5.4.1崖堤、下載etcd二進制文件

mkdir /root/liu/package && cd /root/liu/package
wget https://github.com/etcd-io/etcd/releases/download/v3.4.9/etcd-v3.4.9-linux-amd64.tar.gz

5.4.2、創(chuàng)建工作目錄并解壓二進制包

mkdir /opt/etcd/{bin,cfg,ssl} -p
tar zxvf /root/liu/package/etcd-v3.4.9-linux-amd64.tar.gz
cp /root/liu/package/etcd-v3.4.9-linux-amd64/{etcd,etcdctl} /opt/etcd/bin/

5.4.3耐床、創(chuàng)建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.145.103:2380"
ETCD_LISTEN_CLIENT_URLS="https://192.168.145.103:2379"
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.145.103:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.145.103:2379"
ETCD_INITIAL_CLUSTER="etcd-1=https://192.168.145.103:2380,etcd-2=https://192.168.145.104:2380,etcd-3=https://192.168.145.105:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"
EOF

5.4.4密幔、配置文件說明：

ETCD_NAME：節(jié)點名稱，集群中唯一
ETCD_DATA_DIR：數(shù)據(jù)目錄
ETCD_LISTEN_PEER_URLS：集群通信監(jiān)聽地址
ETCD_LISTEN_CLIENT_URLS：客戶端訪問監(jiān)聽地址
ETCD_INITIAL_ADVERTISE_PEERURLS：集群通告地址
ETCD_ADVERTISE_CLIENT_URLS：客戶端通告地址
ETCD_INITIAL_CLUSTER：集群節(jié)點地址
ETCD_INITIALCLUSTER_TOKEN：集群Token
ETCD_INITIALCLUSTER_STATE：加入集群的當前狀態(tài)撩轰，new是新集群胯甩，existing表示加入已有集群

5.4.5、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

5.4.6堪嫂、拷貝生成的證書至指定位置

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

5.4.7偎箫、啟動并設(shè)置開機啟動

systemctl daemon-reload
systemctl start etcd
systemctl enable etcd

5.4.8、將上面節(jié)點1所有生成的文件拷貝到節(jié)點2和節(jié)點3(創(chuàng)建2和3節(jié)點工作路勁)

scp -r /opt/etcd/ etcd-2:/opt/
scp /usr/lib/systemd/system/etcd.service etcd-2:/usr/lib/systemd/system/
scp -r /opt/etcd/ etcd-3:/opt/
scp /usr/lib/systemd/system/etcd.service etcd-3:/usr/lib/systemd/system/

5.4.9皆串、在節(jié)點2和節(jié)點3分別修改etcd.conf配置文件中的節(jié)點名稱和當前服務(wù)器IP

節(jié)點2
vim /opt/etcd/cfg/etcd.conf

#[Member]
ETCD_NAME="etcd-2"   # 修改此處淹办，節(jié)點2改為etcd-2，節(jié)點3改為etcd-3
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="192.168.145.104:2380"   # 修改此處為當前服務(wù)器IP
ETCD_LISTEN_CLIENT_URLS="https://192.168.145.104:2379" # 修改此處為當前服務(wù)器IP
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.145.104:2380" # 修改此處為當前服務(wù)器IP
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.145.104:2379" # 修改此處為當前服務(wù)器IP
ETCD_INITIAL_CLUSTER="etcd-1=https://192.168.145.103:2380,etcd-2=https://192.168.145.104:2380,etcd-3=https://192.168.145.105:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

節(jié)點3
vim /opt/etcd/cfg/etcd.conf

#[Member]
ETCD_NAME="etcd-3"   # 修改此處愚战，節(jié)點2改為etcd-2娇唯，節(jié)點3改為etcd-3
ETCD_DATA_DIR="/var/lib/etcd/default.etcd"
ETCD_LISTEN_PEER_URLS="192.168.145.105:2380"   # 修改此處為當前服務(wù)器IP
ETCD_LISTEN_CLIENT_URLS="https://192.168.145.105:2379" # 修改此處為當前服務(wù)器IP
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://192.168.145.105:2380" # 修改此處為當前服務(wù)器IP
ETCD_ADVERTISE_CLIENT_URLS="https://192.168.145.105:2379" # 修改此處為當前服務(wù)器IP
ETCD_INITIAL_CLUSTER="etcd-1=https://192.168.145.103:2380,etcd-2=https://10.0.0.72192.168.145.104:2380,etcd-3=https://192.168.145.105:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"

5.4.10齐遵、啟動etcd并設(shè)置開機啟動

systemctl daemon-reload
systemctl start etcd
systemctl enable etcd

5.4.11寂玲、查看集群狀態(tài)

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.145.103:2379,https://193.168.145.104:2379,https://192.168.145.105:2379" endpoint health --write-out=table
+------------------------------+--------+------------+-------+
|           ENDPOINT           | HEALTH |    TOOK    | ERROR |
+------------------------------+--------+------------+-------+
| https://192.168.145.103:2379 |   true | 9.054571ms |       |
+------------------------------+--------+------------+-------+
| https://192.168.145.104:2379 |   true | 9.054571ms |       |
+------------------------------+--------+------------+-------+
| https://192.168.145.105:2379 |   true | 9.054571ms |       |
+------------------------------+--------+------------+-------+

5.4.12、報錯查看思路

journalctl -u etcd -l
systemctl status etcd
cat /var/log/message

6梗摇、安裝docker(這里選擇二進制安裝方式)(master和node節(jié)點)

6.1拓哟、下載并安裝

cd /root/liu/package
wget https://download.docker.com/linux/static/stable/x86_64/docker-19.03.9.tgz
解壓二進制軟件包
tar zxvf docker-19.03.9.tgz
cp  docker/* /usr/bin
docker version

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

6.3伶授、啟動

systemctl daemon-reload
systemctl start docker
systemctl enable docker

6.4断序、配置加速地址

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

systemctl restart docker

7、部署kube-apiserver

7.1糜烹、自簽證書簽發(fā)機構(gòu)（CA）

cd /root/liu/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

生成證書：生成ca.pem和ca-key.pem文件
cfssl gencert -initca ca-csr.json | cfssljson -bare ca -

7.2违诗、使用自簽CA簽發(fā)kube-apiserver HTTPS證書

cat > server-csr.json << EOF
{
    "CN": "kubernetes",
    "hosts": [
      "10.0.0.1",
      "127.0.0.1",
      "192.168.145.100",
      "192.168.145.101",
      "192.168.145.102",
      "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為所有節(jié)點IP
生成證書，生成server.pem和server-key.pem
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes server-csr.json | cfssljson -bare server

7.3疮蹦、下載并解壓二進制軟件包

cd /root/liu/package
wget https://dl.k8s.io/v1.20.4/kubernetes-server-linux-amd64.tar.gz
mkdir -p /opt/kubernetes/{bin,cfg,ssl,logs} 
tar zxvf kubernetes-server-linux-amd64.tar.gz
cd kubernetes/server/bin
cp kube-apiserver kube-scheduler kube-controller-manager /opt/kubernetes/bin
cp kubectl /usr/bin/

7.4诸迟、創(chuàng)建配置文件

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.145.103:2379,https://192.168.145.104:2379,https://192.168.145.105:2379 \\
--bind-address=192.168.145.100 \\
--secure-port=6443 \\
--advertise-address=192.168.145.100 \\
--allow-privileged=true \\
--service-cluster-ip-range=10.0.0.0/24 \\
--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,NodeRestriction \\
--authorization-mode=RBAC,Node \\
--enable-bootstrap-token-auth=true \\
--token-auth-file=/opt/kubernetes/cfg/token.csv \\
--service-node-port-range=30000-32767 \\
--kubelet-client-certificate=/opt/kubernetes/ssl/server.pem \\
--kubelet-client-key=/opt/kubernetes/ssl/server-key.pem \\
--tls-cert-file=/opt/kubernetes/ssl/server.pem  \\
--tls-private-key-file=/opt/kubernetes/ssl/server-key.pem \\
--client-ca-file=/opt/kubernetes/ssl/ca.pem \\
--service-account-key-file=/opt/kubernetes/ssl/ca-key.pem \\
--service-account-issuer=api \\
--service-account-signing-key-file=/opt/kubernetes/ssl/server-key.pem \\
--etcd-cafile=/opt/etcd/ssl/ca.pem \\
--etcd-certfile=/opt/etcd/ssl/server.pem \\
--etcd-keyfile=/opt/etcd/ssl/server-key.pem \\
--requestheader-client-ca-file=/opt/kubernetes/ssl/ca.pem \\
--proxy-client-cert-file=/opt/kubernetes/ssl/server.pem \\
--proxy-client-key-file=/opt/kubernetes/ssl/server-key.pem \\
--requestheader-allowed-names=kubernetes \\
--requestheader-extra-headers-prefix=X-Remote-Extra- \\
--requestheader-group-headers=X-Remote-Group \\
--requestheader-username-headers=X-Remote-User \\
--enable-aggregator-routing=true \\
--audit-log-maxage=30 \\
--audit-log-maxbackup=3 \\
--audit-log-maxsize=100 \\
--audit-log-path=/opt/kubernetes/logs/k8s-audit.log"
EOF

7.5、注：上面兩個\ \ 第一個是轉(zhuǎn)義符，第二個是換行符阵苇，使用轉(zhuǎn)義符是為了使用EOF保留換行符

7.6壁公、參數(shù)說明

--logtostderr：啟用日志

--v：日志等級

--log-dir：日志目錄

--etcd-servers：etcd集群地址

--bind-address：監(jiān)聽地址

--secure-port：https安全端口

--advertise-address：集群通告地址

--allow-privileged：啟用授權(quán)

--service-cluster-ip-range：Service虛擬IP地址段

--enable-admission-plugins：準入控制模塊

--authorization-mode：認證授權(quán)，啟用RBAC授權(quán)和節(jié)點自管理

--enable-bootstrap-token-auth：啟用TLS bootstrap機制

--token-auth-file：bootstrap token文件

--service-node-port-range：Service nodeport類型默認分配端口范圍

--kubelet-client-xxx：apiserver訪問kubelet客戶端證書

--tls-xxx-file：apiserver https證書

1.20版本必須加的參數(shù)：--service-account-issuer绅项，--service-account-signing-key-file

--etcd-xxxfile：連接Etcd集群證書

--audit-log-xxx：審計日志
啟動聚合層相關(guān)配置：--requestheader-client-ca-file紊册，--proxy-client-cert-file，--proxy-client-key-file快耿，--requestheader-allowed-names囊陡，--requestheader-extra-headers-prefix，--requestheader-group-headers掀亥，--requestheader-username-headers关斜，--enable-aggregator-routing

把剛才生成的證書拷貝到配置文件中的路徑
cp /root/liu/k8s/ca*pem /root/liu/k8s/server*pem /opt/kubernetes/ssl/

7.7、啟用 TLS Bootstrapping 機制

TLS Bootstraping：Master apiserver啟用TLS認證后铺浇，Node節(jié)點kubelet和kube-proxy要與kube-apiserver進行通信痢畜，必須使用CA簽發(fā)的有效證書才可以，當Node節(jié)點很多時鳍侣，這種客戶端證書頒發(fā)需要大量工作丁稀，同樣也會增加集群擴展復(fù)雜度。為了簡化流程倚聚，Kubernetes引入了TLS bootstraping機制來自動頒發(fā)客戶端證書线衫，kubelet會以一個低權(quán)限用戶自動向apiserver申請證書，kubelet的證書由apiserver動態(tài)簽署惑折。所以強烈建議在Node上使用這種方式授账，目前主要用于kubelet，kube-proxy還是由我們統(tǒng)一頒發(fā)一個證書惨驶。

7.8白热、TLS bootstraping 工作流程

在這里插入圖片描述

7.9、創(chuàng)建token文件

7.9.1粗卜、自行生成token

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

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

7.10屋确、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

7.11、啟動并設(shè)置開機啟動

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

7.12续扔、注意：如果啟動報錯攻臀，查看是否與etcd連接不上，注意配置文件字符

journalctl -u kube-apiserver -l //查看報錯詳細信息

8纱昧、部署kube-controller-manager

8.1刨啸、創(chuàng)建配置文件

cat > /opt/kubernetes/cfg/kube-controller-manager.conf << EOF
KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=false \\
--v=2 \\
--log-dir=/opt/kubernetes/logs \\
--leader-elect=true \\
--kubeconfig=/opt/kubernetes/cfg/kube-controller-manager.kubeconfig \\
--bind-address=127.0.0.1 \\
--allocate-node-cidrs=true \\
--cluster-cidr=10.244.0.0/16 \\
--service-cluster-ip-range=10.0.0.0/24 \\
--cluster-signing-cert-file=/opt/kubernetes/ssl/ca.pem \\
--cluster-signing-key-file=/opt/kubernetes/ssl/ca-key.pem  \\
--root-ca-file=/opt/kubernetes/ssl/ca.pem \\
--service-account-private-key-file=/opt/kubernetes/ssl/ca-key.pem \\
--cluster-signing-duration=87600h0m0s"
EOF

8.2、配置說明

--kubeconfig：連接apiserver配置文件
--leader-elect：當該組件啟動多個時识脆，自動選舉（HA）
--cluster-signing-cert-file/--cluster-signing-key-file：自動為kubelet頒發(fā)證書的CA设联，與apiserver保持一致

8.3加匈、生成kubeconfig文件

生成kube-controller-manager證書

cd /root/liu/k8s

# 創(chuàng)建證書請求文件
cat > kube-controller-manager-csr.json << EOF
{
  "CN": "system:kube-controller-manager",
  "hosts": [],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "L": "BeiJing", 
      "ST": "BeiJing",
      "O": "system:masters",
      "OU": "System"
    }
  ]
}
EOF
生成證書
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes kube-controller-manager-csr.json | cfssljson -bare kube-controller-manager

8.4、生成kubeconfig文件（以下是shell命令仑荐，直接在終端執(zhí)行）

kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server="https://192.168.145.100:6443" \
  --kubeconfig="/opt/kubernetes/cfg/kube-controller-manager.kubeconfig"
  
kubectl config set-credentials kube-controller-manager \
  --client-certificate=./kube-controller-manager.pem \
  --client-key=./kube-controller-manager-key.pem \
  --embed-certs=true \
  --kubeconfig="/opt/kubernetes/cfg/kube-controller-manager.kubeconfig"
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user=kube-controller-manager \
  --kubeconfig="/opt/kubernetes/cfg/kube-controller-manager.kubeconfig"
  
kubectl config use-context default --kubeconfig="/opt/kubernetes/cfg/kube-controller-manager.kubeconfig"

8.5雕拼、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

8.6、啟動并設(shè)置開機啟動

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

9粘招、部署kube-scheduler

9.1啥寇、創(chuàng)建配置文件

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

9.2、生成kubeconfig文件

cd  /root/liu/k8s

# 創(chuàng)建證書請求文件
cat > kube-scheduler-csr.json << EOF
{
  "CN": "system:kube-scheduler",
  "hosts": [],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "L": "BeiJing",
      "ST": "BeiJing",
      "O": "system:masters",
      "OU": "System"
    }
  ]
}
EOF

# 生成證書
cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=kubernetes kube-scheduler-csr.json | cfssljson -bare kube-scheduler

9.3洒扎、成kubeconfig文件（以下是shell命令辑甜，直接在終端執(zhí)行）

kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server="https://192.168.145.100:6443" \
  --kubeconfig=/opt/kubernetes/cfg/kube-scheduler.kubeconfig
  
kubectl config set-credentials kube-scheduler \
  --client-certificate=./kube-scheduler.pem \
  --client-key=./kube-scheduler-key.pem \
  --embed-certs=true \
  --kubeconfig=/opt/kubernetes/cfg/kube-scheduler.kubeconfig
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user=kube-scheduler \
  --kubeconfig=/opt/kubernetes/cfg/kube-scheduler.kubeconfig
  
kubectl config use-context default --kubeconfig=/opt/kubernetes/cfg/kube-scheduler.kubeconfig

9.4、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

9.5袍冷、啟動并設(shè)置開機啟動

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

10磷醋、查看集群狀態(tài)

10.1、生成kubectl連接集群的證書

cd /root/liu/k8s
cat > admin-csr.json <<EOF
{
  "CN": "admin",
  "hosts": [],
  "key": {
    "algo": "rsa",
    "size": 2048
  },
  "names": [
    {
      "C": "CN",
      "L": "BeiJing",
      "ST": "BeiJing",
      "O": "system:masters",
      "OU": "System"
    }
  ]
}
EOF

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

10.2胡诗、生成kubeconfig文件

mkdir /root/.kube

kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server="https://192.168.145.100:6443" \
  --kubeconfig="/root/.kube/config"
  
kubectl config set-credentials cluster-admin \
  --client-certificate=./admin.pem \
  --client-key=./admin-key.pem \
  --embed-certs=true \
  --kubeconfig="/root/.kube/config"
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user=cluster-admin \
  --kubeconfig="/root/.kube/config"
  
kubectl config use-context default --kubeconfig="/root/.kube/config"

10.3邓线、通過kubectl工具查看當前集群組件狀態(tài)

kubectl get cs

Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE             ERROR
scheduler            Healthy   ok                  
controller-manager   Healthy   ok                  
etcd-2               Healthy   {"health":"true"}   
etcd-1               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}

10.4、授權(quán)kubelet-bootstrap用戶允許請求證書

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

11煌恢、部署Worker Node(還是在master上操作)

11.1骇陈、創(chuàng)建工作目錄并拷貝二進制文件

# 在所有worker node創(chuàng)建工作目錄（master已創(chuàng)建，新加入節(jié)點需要創(chuàng)建）
mkdir -p /opt/kubernetes/{bin,cfg,ssl,logs}

# 從解壓的k8s server壓縮包中拷貝文件
cd /root/liu/package/kubernetes/server/bin
cp kubelet kube-proxy /opt/kubernetes/bin

11.2瑰抵、部署kubelet你雌、創(chuàng)建配置文件

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

11.3、參數(shù)說明

--hostname-override：顯示名稱二汛，集群中唯一
--network-plugin：啟用CNI
--kubeconfig：空路徑婿崭，會自動生成，后面用于連接apiserver
--bootstrap-kubeconfig：首次啟動向apiserver申請證書
--config：配置參數(shù)文件
--cert-dir：kubelet證書生成目錄
--pod-infra-container-image：管理Pod網(wǎng)絡(luò)容器的鏡像

11.4肴颊、配置參數(shù)文件

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

11.5氓栈、生成kubelet初次加入集群引導(dǎo)kubeconfig文件

# 生成 kubelet bootstrap kubeconfig 配置文件
kubectl config set-cluster kubernetes \
  --certificate-authority=/opt/kubernetes/ssl/ca.pem \
  --embed-certs=true \
  --server="https://192.168.145.100:6443" \
  --kubeconfig="/opt/kubernetes/cfg/bootstrap.kubeconfig"
  
kubectl config set-credentials "kubelet-bootstrap" \
  --token="5ec291f50943b0b8d4e5d879b656328a" \
  --kubeconfig="/opt/kubernetes/cfg/bootstrap.kubeconfig"
  
kubectl config set-context default \
  --cluster=kubernetes \
  --user="kubelet-bootstrap" \
  --kubeconfig="/opt/kubernetes/cfg/bootstrap.kubeconfig"
  
kubectl config use-context default --kubeconfig="/opt/kubernetes/cfg/bootstrap.kubeconfig"

11.6、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

11.7苫昌、啟動并設(shè)置開機啟動

systemctl daemon-reload
systemctl start kubelet
systemctl enable kubelet

11.8颤绕、批準kubelet證書申請并加入集群

查看kubelet證書請求
kubectl get csr
NAME                                                   AGE   SIGNERNAME                                    REQUESTOR           CONDITION
node-csr-9c-gV7fhdyBFpybXgaZXXEj8ZUr6z9UwmY5TT49jCJ8  62s   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Pending

批準申請
kubectl certificate approve node-csr-9c-gV7fhdyBFpybXgaZXXEj8ZUr6z9UwmY5TT49jCJ8

查看節(jié)點（由于網(wǎng)絡(luò)插件還沒有部署幸海，節(jié)點會沒有準備就緒 NotReady）
kubectl get node
NAME          STATUS     ROLES    AGE   VERSION
master   NotReady   <none>   10s    v1.20.4

11.9祟身、部署kube-proxy、創(chuàng)建配置文件

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

11.10物独、配置參數(shù)文件

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

11.11袜硫、生成kube-proxy.kubeconfig文件

生成kube-proxy證書

cd /root/liu/k8s

創(chuàng)建證書請求文件
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

11.12、生成kubeconfig文件

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

11.13挡篓、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

11.14婉陷、啟動并設(shè)置開機啟動

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

12帚称、部署網(wǎng)絡(luò)組件Calico

下載地址：https://docs.projectcalico.org/

[root@master yaml]# kubectl apply -f calico.yaml
[root@master yaml]# kubectl get pods -n kube-system
NAME                                       READY   STATUS    RESTARTS   AGE
calico-kube-controllers-756dd4db79-2k24z   1/1     Running   1          2d9h
calico-node-6zh89                          1/1     Running   0          41h
calico-node-7f7zh                          1/1     Running   0          41h
calico-node-c6ss8                          1/1     Running   1          2d9h

13、授權(quán)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

14秽澳、拷貝已部署好的Node相關(guān)文件到新節(jié)點(node1闯睹、node2)

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

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

14.1、刪除kubelet證書和kubeconfig文件(node1担神、node2)

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

14.2楼吃、修改配置文件中的主機名(node1、node2)

node1節(jié)點
vim /opt/kubernetes/cfg/kubelet.conf
--hostname-override=k8s-node1

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

node2節(jié)點
vim /opt/kubernetes/cfg/kubelet.conf
--hostname-override=k8s-node2

vim /opt/kubernetes/cfg/kube-proxy-config.yml
hostnameOverride: k8s-node2

14.3妄讯、啟動并設(shè)置開機啟動(node1孩锡、node2)

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

14.4、在Master上批準新Node kubelet證書申請

kubectl get csr
NAME                                                   AGE   SIGNERNAME                                    REQUESTOR           CONDITION
node-csr-9c-g2f5guyBFpybXgaZXXEj8ZUr6z9UwmYHT835TT49jAJ9  62s   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Pending
node-csr-XoaRNKKNZAPfkzhVF93gtog9Hj1342XqqWcngsWa0ZnW0dQ  62s   kubernetes.io/kube-apiserver-client-kubelet   kubelet-bootstrap   Pending

批準申請
kubectl certificate approve node-csr-9c-g2f5gyBFpybXgaZXXEj8ZUr6z9UwmYHT835TT49jAJ9
kubectl certificate approve node-csr-XoaRNKKNZAPfkzhVF93gtog9Hj1342XqqWcngsWa0ZnW0dQ

[root@k8s-master1 ~]# kubectl get no
NAME          STATUS   ROLES    AGE     VERSION
k8s-master1   Ready    <none>   2d10h   v1.20.4
k8s-node1     Ready    <none>   41h     v1.20.4
k8s-node2     Ready    <none>   41h     v1.20.4

15亥贸、部署CoreDNS和Dashboard

15.1躬窜、部署CoreDNS、準備coredns.yaml文件

# Warning: This is a file generated from the base underscore template file: coredns.yaml.base

apiVersion: v1
kind: ServiceAccount
metadata:
  name: coredns
  namespace: kube-system
  labels:
      kubernetes.io/cluster-service: "true"
      addonmanager.kubernetes.io/mode: Reconcile
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  labels:
    kubernetes.io/bootstrapping: rbac-defaults
    addonmanager.kubernetes.io/mode: Reconcile
  name: system:coredns
rules:
- apiGroups:
  - ""
  resources:
  - endpoints
  - services
  - pods
  - namespaces
  verbs:
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - nodes
  verbs:
  - get
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  annotations:
    rbac.authorization.kubernetes.io/autoupdate: "true"
  labels:
    kubernetes.io/bootstrapping: rbac-defaults
    addonmanager.kubernetes.io/mode: EnsureExists
  name: system:coredns
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: system:coredns
subjects:
- kind: ServiceAccount
  name: coredns
  namespace: kube-system
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: coredns
  namespace: kube-system
  labels:
      addonmanager.kubernetes.io/mode: EnsureExists
data:
  Corefile: |
    .:53 {
        log
        errors
        health {
            lameduck 5s
        }
        ready
        kubernetes cluster.local in-addr.arpa ip6.arpa {
            pods insecure
            fallthrough in-addr.arpa ip6.arpa
            ttl 30
        }
        prometheus :9153
        forward . /etc/resolv.conf
        cache 30
        loop
        reload
        loadbalance
    }
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: coredns
  namespace: kube-system
  labels:
    k8s-app: kube-dns
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: Reconcile
    kubernetes.io/name: "CoreDNS"
spec:
  # replicas: not specified here:
  # 1. In order to make Addon Manager do not reconcile this replicas parameter.
  # 2. Default is 1.
  # 3. Will be tuned in real time if DNS horizontal auto-scaling is turned on.
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 1
  selector:
    matchLabels:
      k8s-app: kube-dns
  template:
    metadata:
      labels:
        k8s-app: kube-dns
      annotations:
        seccomp.security.alpha.kubernetes.io/pod: 'runtime/default'
    spec:
      priorityClassName: system-cluster-critical
      serviceAccountName: coredns
      tolerations:
        - key: "CriticalAddonsOnly"
          operator: "Exists"
      nodeSelector:
        kubernetes.io/os: linux
      containers:
      - name: coredns
        image: lizhenliang/coredns:1.6.7
        imagePullPolicy: IfNotPresent
        resources:
          limits:
            memory: 512Mi 
          requests:
            cpu: 100m
            memory: 70Mi
        args: [ "-conf", "/etc/coredns/Corefile" ]
        volumeMounts:
        - name: config-volume
          mountPath: /etc/coredns
          readOnly: true
        ports:
        - containerPort: 53
          name: dns
          protocol: UDP
        - containerPort: 53
          name: dns-tcp
          protocol: TCP
        - containerPort: 9153
          name: metrics
          protocol: TCP
        livenessProbe:
          httpGet:
            path: /health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 60
          timeoutSeconds: 5
          successThreshold: 1
          failureThreshold: 5
        readinessProbe:
          httpGet:
            path: /ready
            port: 8181
            scheme: HTTP
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            add:
            - NET_BIND_SERVICE
            drop:
            - all
          readOnlyRootFilesystem: true
      dnsPolicy: Default
      volumes:
        - name: config-volume
          configMap:
            name: coredns
            items:
            - key: Corefile
              path: Corefile
---
apiVersion: v1
kind: Service
metadata:
  name: kube-dns
  namespace: kube-system
  annotations:
    prometheus.io/port: "9153"
    prometheus.io/scrape: "true"
  labels:
    k8s-app: kube-dns
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: Reconcile
    kubernetes.io/name: "CoreDNS"
spec:
  selector:
    k8s-app: kube-dns
  clusterIP: 10.0.0.2 
  ports:
  - name: dns
    port: 53
    protocol: UDP
  - name: dns-tcp
    port: 53
    protocol: TCP
  - name: metrics
    port: 9153
    protocol: TCP

[root@k8s-master1 yaml]# kubectl get po -n kube-system 
NAME                                       READY   STATUS    RESTARTS   AGE
calico-kube-controllers-756dd4db79-2k24z   1/1     Running   1          2d10h
calico-node-6zh89                          1/1     Running   0          41h
calico-node-7f7zh                          1/1     Running   0          41h
calico-node-c6ss8                          1/1     Running   1          2d10h
coredns-6cc56c94bd-vbdg7                   1/1     Running   0          17m

15.2炕置、部署Dashboard荣挨、準備dashboard.yaml文件

# Copyright 2017 The Kubernetes Authors.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

apiVersion: v1
kind: Namespace
metadata:
  name: kubernetes-dashboard

---

apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard

---

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

---

apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-certs
  namespace: kubernetes-dashboard
type: Opaque

---

apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-csrf
  namespace: kubernetes-dashboard
type: Opaque
data:
  csrf: ""

---

apiVersion: v1
kind: Secret
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-key-holder
  namespace: kubernetes-dashboard
type: Opaque

---

kind: ConfigMap
apiVersion: v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard-settings
  namespace: kubernetes-dashboard

---

kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
rules:
  # Allow Dashboard to get, update and delete Dashboard exclusive secrets.
  - apiGroups: [""]
    resources: ["secrets"]
    resourceNames: ["kubernetes-dashboard-key-holder", "kubernetes-dashboard-certs", "kubernetes-dashboard-csrf"]
    verbs: ["get", "update", "delete"]
    # Allow Dashboard to get and update 'kubernetes-dashboard-settings' config map.
  - apiGroups: [""]
    resources: ["configmaps"]
    resourceNames: ["kubernetes-dashboard-settings"]
    verbs: ["get", "update"]
    # Allow Dashboard to get metrics.
  - apiGroups: [""]
    resources: ["services"]
    resourceNames: ["heapster", "dashboard-metrics-scraper"]
    verbs: ["proxy"]
  - apiGroups: [""]
    resources: ["services/proxy"]
    resourceNames: ["heapster", "http:heapster:", "https:heapster:", "dashboard-metrics-scraper", "http:dashboard-metrics-scraper"]
    verbs: ["get"]

---

kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
rules:
  # Allow Metrics Scraper to get metrics from the Metrics server
  - apiGroups: ["metrics.k8s.io"]
    resources: ["pods", "nodes"]
    verbs: ["get", "list", "watch"]

---

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: kubernetes-dashboard
subjects:
  - kind: ServiceAccount
    name: kubernetes-dashboard
    namespace: kubernetes-dashboard

---

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: kubernetes-dashboard
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: kubernetes-dashboard
subjects:
  - kind: ServiceAccount
    name: kubernetes-dashboard
    namespace: kubernetes-dashboard

---

kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kubernetes-dashboard
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: kubernetes-dashboard
  template:
    metadata:
      labels:
        k8s-app: kubernetes-dashboard
    spec:
      containers:
        - name: kubernetes-dashboard
          image: kubernetesui/dashboard:v2.0.3
          imagePullPolicy: Always
          ports:
            - containerPort: 8443
              protocol: TCP
          args:
            - --auto-generate-certificates
            - --namespace=kubernetes-dashboard
            # Uncomment the following line to manually specify Kubernetes API server Host
            # If not specified, Dashboard will attempt to auto discover the API server and connect
            # to it. Uncomment only if the default does not work.
            # - --apiserver-host=http://my-address:port
          volumeMounts:
            - name: kubernetes-dashboard-certs
              mountPath: /certs
              # Create on-disk volume to store exec logs
            - mountPath: /tmp
              name: tmp-volume
          livenessProbe:
            httpGet:
              scheme: HTTPS
              path: /
              port: 8443
            initialDelaySeconds: 30
            timeoutSeconds: 30
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            runAsUser: 1001
            runAsGroup: 2001
      volumes:
        - name: kubernetes-dashboard-certs
          secret:
            secretName: kubernetes-dashboard-certs
        - name: tmp-volume
          emptyDir: {}
      serviceAccountName: kubernetes-dashboard
      nodeSelector:
        "kubernetes.io/os": linux
      # Comment the following tolerations if Dashboard must not be deployed on master
      tolerations:
        - key: node-role.kubernetes.io/master
          effect: NoSchedule

---

kind: Service
apiVersion: v1
metadata:
  labels:
    k8s-app: dashboard-metrics-scraper
  name: dashboard-metrics-scraper
  namespace: kubernetes-dashboard
spec:
  ports:
    - port: 8000
      targetPort: 8000
  selector:
    k8s-app: dashboard-metrics-scraper

---

kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    k8s-app: dashboard-metrics-scraper
  name: dashboard-metrics-scraper
  namespace: kubernetes-dashboard
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: dashboard-metrics-scraper
  template:
    metadata:
      labels:
        k8s-app: dashboard-metrics-scraper
      annotations:
        seccomp.security.alpha.kubernetes.io/pod: 'runtime/default'
    spec:
      containers:
        - name: dashboard-metrics-scraper
          image: kubernetesui/metrics-scraper:v1.0.4
          ports:
            - containerPort: 8000
              protocol: TCP
          livenessProbe:
            httpGet:
              scheme: HTTP
              path: /
              port: 8000
            initialDelaySeconds: 30
            timeoutSeconds: 30
          volumeMounts:
          - mountPath: /tmp
            name: tmp-volume
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            runAsUser: 1001
            runAsGroup: 2001
      serviceAccountName: kubernetes-dashboard
      nodeSelector:
        "kubernetes.io/os": linux
      # Comment the following tolerations if Dashboard must not be deployed on master
      tolerations:
        - key: node-role.kubernetes.io/master
          effect: NoSchedule
      volumes:
        - name: tmp-volume
          emptyDir: {}

kubectl apply -f dashboard.yaml
kubectl get pod -n kube-system
NAMESPACE              NAME                                         READY   STATUS    RESTARTS   AGE     IP                NODE          NOMINATED NODE   READINESS GATES
kube-system            calico-kube-controllers-756dd4db79-2k24z     1/1     Running   1          2d10h   172.16.159.130    k8s-master1   <none>           <none>
kube-system            calico-node-6zh89                            1/1     Running   0          42h     192.168.145.101   k8s-node1     <none>           <none>
kube-system            calico-node-7f7zh                            1/1     Running   0          42h     192.168.145.102   k8s-node2     <none>           <none>
kube-system            calico-node-c6ss8                            1/1     Running   1          2d10h   192.168.145.100   k8s-master1   <none>           <none>
kube-system            coredns-6cc56c94bd-vbdg7                     1/1     Running   0          39m     172.16.36.65      k8s-node1     <none>           <none>
kubernetes-dashboard   dashboard-metrics-scraper-7b59f7d4df-bmgw6   1/1     Running   0          18m     172.16.36.66      k8s-node1     <none>           <none>
kubernetes-dashboard   kubernetes-dashboard-5dbf55bd9d-fcpbl        1/1     Running   0          18m     172.16.169.129    k8s-node2     <none>           <none>

kubectl get svc -A
NAMESPACE              NAME                        TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
default                kubernetes                  ClusterIP   10.0.0.1     <none>        443/TCP                  2d11h
kube-system            kube-dns                    ClusterIP   10.0.0.2     <none>        53/UDP,53/TCP,9153/TCP   41m
kubernetes-dashboard   dashboard-metrics-scraper   ClusterIP   10.0.0.229   <none>        8000/TCP                 19m
kubernetes-dashboard   kubernetes-dashboard        NodePort    10.0.0.242   <none>        443:30001/TCP            19m

15.3、訪問地址：https://NodeIP:30001

15.4朴摊、創(chuàng)建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}')

在這里插入圖片描述

至此二進制k8s單節(jié)點集群搭建完畢

最后編輯于：2021.12.19 17:50:44

?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者

人面猴
序言：七十年代末垦沉，一起剝皮案震驚了整個濱河市，隨后出現(xiàn)的幾起案子仍劈，更是在濱河造成了極大的恐慌厕倍，老刑警劉巖，帶你破解...
沈念sama閱讀 206,214評論 6贊 481
死咒
序言：濱河連續(xù)發(fā)生了三起死亡事件贩疙，死亡現(xiàn)場離奇詭異讹弯，居然都是意外死亡，警方通過查閱死者的電腦和手機这溅，發(fā)現(xiàn)死者居然都...
沈念sama閱讀 88,307評論 2贊 382
救了他兩次的神仙讓他今天三更去死
文/潘曉璐我一進店門组民，熙熙樓的掌柜王于貴愁眉苦臉地迎上來，“玉大人悲靴，你說我怎么就攤上這事臭胜。” “怎么了癞尚？”我有些...
開封第一講書人閱讀 152,543評論 0贊 341
道士緝兇錄：失蹤的賣姜人
文/不壞的土叔我叫張陵耸三，是天一觀的道長。經(jīng)常有香客問我浇揩，道長仪壮，這世上最難降的妖魔是什么？我笑而不...
開封第一講書人閱讀 55,221評論 1贊 279
?港島之戀（遺憾婚禮）
正文為了忘掉前任胳徽，我火速辦了婚禮积锅，結(jié)果婚禮上爽彤，老公的妹妹穿的比我還像新娘。我一直安慰自己缚陷，他們只是感情好适篙，可當我...
茶點故事閱讀 64,224評論 5贊 371
惡毒庶女頂嫁案：這布局不是一般人想出來的
文/花漫我一把揭開白布。她就那樣靜靜地躺著箫爷，像睡著了一般匙瘪。火紅的嫁衣襯著肌膚如雪。梳的紋絲不亂的頭發(fā)上蝶缀，一...
開封第一講書人閱讀 49,007評論 1贊 284
城市分裂傳說
那天丹喻，我揣著相機與錄音，去河邊找鬼翁都。笑死碍论，一個胖子當著我的面吹牛，可吹牛的內(nèi)容都是我干的柄慰。我是一名探鬼主播鳍悠，決...
沈念sama閱讀 38,313評論 3贊 399
雙鴛鴦連環(huán)套：你想象不到人心有多黑
文/蒼蘭香墨我猛地睜開眼，長吁一口氣：“原來是場噩夢啊……” “哼坐搔！你這毒婦竟也來了藏研？” 一聲冷哼從身側(cè)響起，我...
開封第一講書人閱讀 36,956評論 0贊 259
萬榮殺人案實錄
序言：老撾萬榮一對情侶失蹤概行，失蹤者是張志新（化名）和其女友劉穎蠢挡，沒想到半個月后，有當?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體凳忙，經(jīng)...
沈念sama閱讀 43,441評論 1贊 300
?護林員之死
正文獨居荒郊野嶺守林人離奇死亡业踏，尸身上長有42處帶血的膿包…… 初始之章·張勛以下內(nèi)容為張勛視角年9月15日...
茶點故事閱讀 35,925評論 2贊 323
?白月光啟示錄
正文我和宋清朗相戀三年，在試婚紗的時候發(fā)現(xiàn)自己被綠了涧卵。大學(xué)時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片勤家。...
茶點故事閱讀 38,018評論 1贊 333
活死人
序言：一個原本活蹦亂跳的男人離奇死亡，死狀恐怖柳恐，靈堂內(nèi)的尸體忽然破棺而出伐脖，到底是詐尸還是另有隱情，我是刑警寧澤乐设，帶...
沈念sama閱讀 33,685評論 4贊 322
?日本核電站爆炸內(nèi)幕
正文年R本政府宣布讼庇，位于F島的核電站，受9級特大地震影響伤提，放射性物質(zhì)發(fā)生泄漏巫俺。R本人自食惡果不足惜，卻給世界環(huán)境...
茶點故事閱讀 39,234評論 3贊 307
男人毒藥：我在死后第九天來索命
文/蒙蒙一肿男、第九天我趴在偏房一處隱蔽的房頂上張望介汹。院中可真熱鬧，春花似錦舶沛、人聲如沸嘹承。這莊子的主人今日做“春日...
開封第一講書人閱讀 30,240評論 0贊 19
一樁弒父案如庭，背后竟有這般陰謀
文/蒼蘭香墨我抬頭看了看天上的太陽叹卷。三九已至，卻和暖如春坪它，著一層夾襖步出監(jiān)牢的瞬間骤竹，已是汗流浹背。一陣腳步聲響...
開封第一講書人閱讀 31,464評論 1贊 261
情欲美人皮
我被黑心中介騙來泰國打工往毡，沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留蒙揣，地道東北人。一個月前我還...
沈念sama閱讀 45,467評論 2贊 352
代替公主和親
正文我出身青樓开瞭，卻偏偏與公主長得像懒震，于是被迫代替她去往敵國和親。傳聞我的和親對象是個殘疾皇子嗤详，可洞房花燭夜當晚...
茶點故事閱讀 42,762評論 2贊 345