部署k8s有多種方式,本章我們采取二進(jìn)制的部署方式來部署k8s集群,二進(jìn)制部署麻煩點，但是可以在我們通過部署各個組件的時候，也通知能讓我們更好的深入了解組件之間的關(guān)聯(lián),也利于后期維護(hù)
主機環(huán)境
- 系統(tǒng): centos7.4 3臺
- 內(nèi)存: 4G
- 磁盤:40G
- cpu 2CPU
軟件版本
- k8s 1.18
- docker 19-ce
主機規(guī)劃
| masetr | 172.16.210.53 | kube-apiserver，kube-controller-manager，kube-scheduler，etcd |
|---|---|---|
| node1 | 172.16.210.54 | kubelet，kube-proxy，docker etcd |
| node2 | 172.16.210.55 | kubelet，kube-proxy，docker etcd |
1.主機環(huán)境初始化
在3個節(jié)點上操作
#關(guān)閉防火墻
systemctl stop firewalld ; systemctl disable firewalld
#關(guān)閉selinux
setenforce 0 ;sed -i 's/enforcing/disabled/' /etc/selinux/config
#關(guān)閉swap分區(qū)
swapoff -a ; sed -ri 's/.*swap.*/#&/' /etc/fstab
#添加hosts
cat >> /etc/hosts << EOF
172.16.210.53 master k8s-master
172.16.210.54 node1 k8s-node1
172.16.210.55 node2 k8s-node2
EOF
#添加防火墻轉(zhuǎn)發(fā)
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
modprobe br_netfilter
sysctl --system ##生效
#時間同步
yum install -y ntpdate ##安裝時間同步工具
ntpdate time.windows.com #同步windwos時間服務(wù)器
2.部署etcd集群
Etcd 是一個分布式鍵值存儲系統(tǒng)，Kubernetes使用Etcd進(jìn)行數(shù)據(jù)存儲
2.1準(zhǔn)備cfssl證書生成工具
cfssl是一個開源的證書管理工具，使用json文件生成證書，相比openssl更方便使用
在master上操作:
##獲取證書管理工具
wget https://pkg.cfssl.org/R1.2/cfssl_linux-amd64
wget https://pkg.cfssl.org/R1.2/cfssljson_linux-amd64
wget https://pkg.cfssl.org/R1.2/cfssl-certinfo_linux-amd64
##添加看執(zhí)行權(quán)限并放進(jìn)可執(zhí)行目錄
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證書
創(chuàng)建證書目錄
mkdir -p ~/TLS/{etcd,k8s}
cd ~/TLS/etcd ##進(jìn)入證書目錄
自簽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 ##可以看到當(dāng)前目錄生成了兩個證書文件
ca-key.pem ca.pem
2. 使用自簽CA簽發(fā)Etcd HTTPS證書
創(chuàng)建證書申請文件：
cat > server-csr.json << EOF
{
"CN": "etcd",
"hosts": [
"172.16.210.53",
"172.16.210.54",
"172.16.210.55"
],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "BeiJing",
"ST": "BeiJing"
}
]
}
EOF
生成證書:
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 ##可以看到生成了兩個sever證書
server-key.pem server.pem
2.3下載etcd二進(jìn)制文件
文件地址:https://github.com/etcd-io/etcd/releases/download/v3.4.9/etcd-v3.4.9-linux-amd64.tar.gz
以下操作在master上操作,待會將master生成的所有文件拷貝到node1和node2:
wget https://github.com/etcd-io/etcd/releases/download/v3.4.9/etcd-v3.4.9-linux-amd64.tar.gz ##獲取二進(jìn)制文件
2.4部署etcd集群
1.創(chuàng)建工作目錄并解壓二進(jìn)制文件
mkdir /opt/etcd/{bin,cfg,ssl} -p
tar zxvf etcd-v3.4.9-linux-amd64.tar.gz
mv etcd-v3.4.9-linux-amd64/{etcd,etcdctl} /opt/etcd/bin/
2.創(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://172.16.210.53:2380"
ETCD_LISTEN_CLIENT_URLS="https://172.16.210.53:2379"
#[Clustering]
ETCD_INITIAL_ADVERTISE_PEER_URLS="https://172.16.210.53:2380"
ETCD_ADVERTISE_CLIENT_URLS="https://172.16.210.53:2379"
ETCD_INITIAL_CLUSTER="etcd-1=https://172.16.210.53:2380,etcd-2=https://172.16.210.54:2380,etcd-3=https://172.16.210.55:2380"
ETCD_INITIAL_CLUSTER_TOKEN="etcd-cluster"
ETCD_INITIAL_CLUSTER_STATE="new"
EOF
參數(shù)詳解:
- ETCD_DATA_DIR：數(shù)據(jù)目錄
- ETCD_LISTEN_PEER_URLS：集群通信監(jiān)聽地址
- ETCD_LISTEN_CLIENT_URLS：客戶端訪問監(jiān)聽地址
- ETCD_INITIAL_ADVERTISE_PEER_URLS：集群通告地址
- ETCD_ADVERTISE_CLIENT_URLS：客戶端通告地址
- ETCD_INITIAL_CLUSTER：集群節(jié)點地址
- ETCD_INITIAL_CLUSTER_TOKEN：集群Token
- ETCD_INITIAL_CLUSTER_STATE：加入集群的當(dāng)前狀態(tài)，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. 拷貝剛才生成的證書
把剛才生成的證書拷貝到配置文件中的路徑：
cp ~/TLS/etcd/ca*pem ~/TLS/etcd/server*pem /opt/etcd/ssl/
5.將master生成的所有文件拷貝到其他節(jié)點
scp -r /opt/etcd/ 172.16.210.54:/opt/
scp /usr/lib/systemd/system/etcd.service 172.16.210.54:/usr/lib/systemd/system/
scp -r /opt/etcd/ 172.16.210.55:/opt/
scp /usr/lib/systemd/system/etcd.service 172.16.210.55:/usr/lib/systemd/system/
6.在node1和node2分別修改etcd.conf配置文件中的節(jié)點名稱和當(dāng)前服務(wù)器IP
sed -i '4,8s/172.16.210.53/172.16.210.54/' /opt/etcd/cfg/etcd.conf ; sed -i '2s/etcd-1/etcd-2/' /opt/etcd/cfg/etcd.conf ###在node1執(zhí)行
sed -i '4,8s/172.16.210.53/172.16.210.55/' /opt/etcd/cfg/etcd.conf ; sed -i '2s/etcd-1/etcd-3/' /opt/etcd/cfg/etcd.conf ###在node2執(zhí)行
7.啟動3個節(jié)點的etcd并加入開機自啟
在三各節(jié)點操作
systemctl daemon-reload
systemctl start etcd
systemctl enable etcd
8.查看etcd集群狀態(tài)
[root@master ~]# ETCDCTL_API=3 /opt/etcd/bin/etcdctl --cacert=/opt/etcd/ssl/ca.pem --cert=/opt/etcd/ssl/server.pem --key=/opt/etcd/ssl/server-key.pem --endpoints="https://172.16.210.53:2379,https://172.16.210.54:2379,https://172.16.210.55:2379" endpoint health
https://172.16.210.54:2379 is healthy: successfully committed proposal: took = 14.194738ms
https://172.16.210.55:2379 is healthy: successfully committed proposal: took = 14.97292ms
https://172.16.210.53:2379 is healthy: successfully committed proposal: took = 14.847968ms
出現(xiàn)successfully,表面etcd部署成功,如果有異常情況可以使用systemctl stautus etcd -l進(jìn)一步查看報錯信息
3.安裝Docker
可以使用yum安裝,這次我們采用二進(jìn)制的方式
以下所有操作在所有節(jié)點
3.1獲取docker安裝包
wget https://download.docker.com/linux/static/stable/x86_64/docker-19.03.9.tgz
3.2解壓docker二進(jìn)制包
tar zxvf docker-19.03.9.tgz
mv docker/* /usr/bin
3.3配置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.4配置docker加速器
mkdir /etc/docker
cat > /etc/docker/daemon.json << EOF
{
"registry-mirrors": ["https://jo6348gu.mirror.aliyuncs.com"]
}
EOF
3.5啟動docker并加入開機自啟
systemctl daemon-reload
systemctl start docker
systemctl enable docker
4.部署master
以下操作在master上
4.1 生成kube-apiserver證書
1. 自簽證書頒發(fā)機構(gòu)（CA）
cd TLS/k8s
cat > ca-config.json << EOF
{
"signing": {
"default": {
"expiry": "87600h"
},
"profiles": {
"kubernetes": {
"expiry": "87600h",
"usages": [
"signing",
"key encipherment",
"server auth",
"client auth"
]
}
}
}
}
EOF
cat > ca-csr.json << EOF
{
"CN": "kubernetes",
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"L": "Beijing",
"ST": "Beijing",
"O": "k8s",
"OU": "System"
}
]
}
EOF
生成證書：
cfssl gencert -initca ca-csr.json | cfssljson -bare ca -
ls *pem
ca-key.pem ca.pem ##可以看到生成了兩個證書
2. 使用自簽CA簽發(fā)kube-apiserver HTTPS證書
創(chuàng)建證書申請文件：
cat > server-csr.json << EOF
{
"CN": "kubernetes",
"hosts": [
"10.0.0.1",
"127.0.0.1",
"172.16.210.53",
"172.16.210.54",
"172.16.210.55",
"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
生成證書:
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 ##可以看到又生成兩個server證書
4.2 從Github下載k8s二進(jìn)制文件并解壓
1.獲取二進(jìn)制包
wget https://dl.k8s.io/v1.18.3/kubernetes-server-linux-amd64.tar.gz
2.解壓二進(jìn)制包
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/
4.3部署kube-apiserver
1. 創(chuàng)建配置文件
cat > /opt/kubernetes/cfg/kube-apiserver.conf << EOF
KUBE_APISERVER_OPTS="--logtostderr=false \\
--v=4 \\
--log-dir=/opt/kubernetes/logs \\
--etcd-servers=https://172.16.210.53:2379,https://172.16.210.54:2379,https://172.16.210.55:2379 \\
--bind-address=172.16.210.53 \\
--secure-port=6443 \\
--advertise-address=172.16.210.53 \\
--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
- 參數(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：準(zhǔn)入控制模塊
- –authorization-mode：認(rèn)證授權(quán)，啟用RBAC授權(quán)和節(jié)點自管理
- –enable-bootstrap-token-auth：啟用TLS bootstrap機制
- –token-auth-file：bootstrap token文件
- –service-node-port-range：Service nodeport類型默認(rèn)分配端口范圍
- –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認(rèn)證后，Node節(jié)點kubelet和kube-proxy要與kube-apiserver進(jìn)行通信，必須使用CA簽發(fā)的有效證書才可以，當(dāng)Node節(jié)點很多時，這種客戶端證書頒發(fā)需要大量工作，同樣也會增加集群擴(kuò)展復(fù)雜度。為了簡化流程，Kubernetes引入了TLS bootstraping機制來自動頒發(fā)客戶端證書，kubelet會以一個低權(quán)限用戶自動向apiserver申請證書，kubelet的證書由apiserver動態(tài)簽署。所以強烈建議在Node上使用這種方式，目前主要用于kubelet，kube-proxy還是由我們統(tǒng)一頒發(fā)一個證書。
TLS bootstraping 工作流程：
image.png
創(chuàng)建上述配置文件中token文件：
cat > /opt/kubernetes/cfg/token.csv << EOF
b1dc586d69159ff4e3ef7efa9db60e48,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. 啟動并設(shè)置開機啟動
systemctl daemon-reload
systemctl start kube-apiserver
systemctl enable kube-apiserver
6. 授權(quán)kubelet-bootstrap用戶允許請求證書
kubectl create clusterrolebinding kubelet-bootstrap \
--clusterrole=system:node-bootstrapper \
--user=kubelet-bootstrap
4.4 部署kube-controller-manager
- 創(chuàng)建配置文件
cat > /opt/kubernetes/cfg/kube-controller-manager.conf << EOF
KUBE_CONTROLLER_MANAGER_OPTS="--logtostderr=false \\
--v=4 \\
--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：當(dāng)該組件啟動多個時，自動選舉（HA）
- –cluster-signing-cert-file/–cluster-signing-key-file：自動為kubelet頒發(fā)證書的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.啟動并設(shè)置開機啟動
systemctl daemon-reload
systemctl start kube-controller-manager
systemctl enable kube-controller-manager
4.6 部署kube-scheduler
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 \
--master=127.0.0.1:8080 \
--bind-address=127.0.0.1"
EOF
- –master：通過本地非安全本地端口8080連接apiserver。
- –leader-elect：當(dāng)該組件啟動多個時，自動選舉（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.啟動并設(shè)置開機啟動
systemctl daemon-reload
systemctl start kube-scheduler
systemctl enable kube-scheduler
4. 查看集群狀態(tài)
所有組件都已經(jīng)啟動成功，通過kubectl get cs命令查看當(dāng)前集群組件狀態(tài)：
kubectl get cs
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
scheduler Healthy ok
etcd-0 Healthy {"health":"true"}
etcd-1 Healthy {"health":"true"}
etcd-2 Healthy {"health":"true"}
五、部署Worker Node
下面還是在master節(jié)點上操作，即同時作為Worker Node
5.1 拷貝二進(jìn)制文件
cd ~/kubernetes/server/bin
cp kubelet kube-proxy /opt/kubernetes/bin
5.2 部署kubelet
1. 創(chuàng)建配置文件
cat > /opt/kubernetes/cfg/kubelet.conf << EOF
KUBELET_OPTS="--logtostderr=false \\
--v=4 \\
--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
參數(shù)詳解:
- –hostname-override：顯示名稱，集群中唯一
- –network-plugin：啟用CNI
- –kubeconfig：空路徑，會自動生成，后面用于連接apiserver
- –bootstrap-kubeconfig：首次啟動向apiserver申請證書
- –config：配置參數(shù)文件
- –cert-dir：kubelet證書生成目錄
- –pod-infra-container-image：管理Pod網(wǎng)絡(luò)容器的鏡像
2. 創(chuàng)建配置參數(shù)yaml文件
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文件
##設(shè)置環(huán)境變量
KUBE_APISERVER="https://172.16.210.53:6443" # apiserver IP:PORT
TOKEN="b1dc586d69159ff4e3ef7efa9db60e48" # 與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. 啟動并設(shè)置開機啟動
systemctl daemon-reload
systemctl start kubelet
systemctl enable kubelet
5.3 批準(zhǔn)kubelet證書申請并加入集群
# 查看kubelet證書請求
kubectl get csr
NAME AGE SIGNERNAME REQUESTOR CONDITION
node-csr-d-UyqVObT-tnWdXd881Ppc3oNVr6xkCBXV7VRlWyhf8 30s kubernetes.io/kube-apiserver-client-kubelet kubelet-bootstrap Pending
# 批準(zhǔn)申請
kubectl certificate approve node-csr-d-UyqVObT-tnWdXd881Ppc3oNVr6xkCBXV7VRlWyhf8
# 查看節(jié)點
kubectl get node
NAME STATUS ROLES AGE VERSION
k8s-master NotReady <none> 15s v1.18.3 ##由于沒有部署網(wǎng)絡(luò)插件,所以節(jié)點是NotReady
5.4 部署kube-proxy
1. 創(chuàng)建配置文件
cat > /opt/kubernetes/cfg/kube-proxy.conf << EOF
KUBE_PROXY_OPTS="--logtostderr=false \\
--v=4 \\
--log-dir=/opt/kubernetes/logs \\
--config=/opt/kubernetes/cfg/kube-proxy-config.yml"
EOF
2. 配置參數(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-master
clusterCIDR: 10.0.0.0/24
EOF
3. 生成kube-proxy.kubeconfig文件
生成kube-proxy證書：
# 切換工作目錄
cd ~/TLS/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
ls kube-proxy*pem
kube-proxy-key.pem kube-proxy.pem ##可以看到生成了兩個kube-proxy的證書文件
生成kubeconfig文件
#創(chuàng)建環(huán)境變量
KUBE_APISERVER="https://172.16.210.53: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. 啟動并設(shè)置開機啟動
systemctl daemon-reload
systemctl start kube-proxy
systemctl enable kube-proxy
5.5 部署CNI網(wǎng)絡(luò)
1.先下載CNI二進(jìn)制文件：
wget https://github.com/containernetworking/plugins/releases/download/v0.8.6/cni-plugins-linux-amd64-v0.8.6.tgz
2.解壓二進(jìn)制包并移動到默認(rèn)工作目錄
mkdir -p /opt/cni/bin
tar zxvf cni-plugins-linux-amd64-v0.8.6.tgz -C /opt/cni/bin
5.5部署CNI網(wǎng)絡(luò)
獲取flanel網(wǎng)絡(luò)yaml文件,并修改鏡像地址
echo "151.101.76.133 raw.githubusercontent.com" >>/etc/hosts
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 ##默認(rèn)鏡像地址無法訪問，修改為docker hub鏡像倉庫。
開始部署CNI網(wǎng)絡(luò)：
kubectl apply -f kube-flannel.yml
##查看pod是否運行成功
kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
kube-flannel-ds-amd64-p9tdp 1/1 Running 0
##運行成功后,再查看節(jié)點是否運行正常
kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-master Ready <none> 19m v1.18.3
5.6 授權(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
5.7增加worke 節(jié)點
1. 拷貝已部署好的Node相關(guān)文件到新節(jié)點
在master節(jié)點將Worker Node涉及文件拷貝到節(jié)點172.16.210..54/55
scp -r /opt/kubernetes root@172.16.210.54:/opt/
scp -r /usr/lib/systemd/system/{kubelet,kube-proxy}.service root@172.16.210.54:/usr/lib/systemd/system
scp -r /opt/cni/ root@172.16.210.54:/opt/
scp /opt/kubernetes/ssl/ca.pem root@172.16.210.54:/opt/kubernetes/ssl
2. 刪除kubelet證書和kubeconfig文件
rm -f /opt/kubernetes/cfg/kubelet.kubeconfig
rm -f /opt/kubernetes/ssl/kubelet*
3. 修改主機名
sed -i 's/k8s-master/k8s-node1/g' /opt/kubernetes/cfg/kubelet.conf /opt/kubernetes/cfg/kube-proxy-config.yml ##加入node2的主機只需要把這條命令的k8s-node1改成k8s-node2即可
4. 啟動并設(shè)置開機啟動
systemctl daemon-reload
systemctl start kubelet
systemctl enable kubelet
systemctl start kube-proxy
systemctl enable kube-proxy
5.在Master上批準(zhǔn)新Node kubelet證書申請
kubectl get csr
NAME AGE SIGNERNAME REQUESTOR CONDITION
node-csr--t2cjSYX0z7ba4Tyh4GCnngZaGBUwmAHyY1xuxU40j0 28s kubernetes.io/kube-apiserver-client-kubelet kubelet-bootstrap Pending
kubectl certificate approve node-csr--t2cjSYX0z7ba4Tyh4GCnngZaGBUwmAHyY1xuxU40j0
6. 查看Node狀態(tài)
kubectl get nodes
NAME STATUS ROLES AGE VERSION
k8s-master Ready <none> 46m v1.18.3
k8s-node1 Ready <none> 8m57s v1.18.3
k8s-node2 Ready <none> 3m59s v1.18.3
Node2（172.16.210.55 ）節(jié)點同上。記得修改主機名
六、部署Dashboard和CoreDNS
Dashboard的部署可以看我另一篇文檔,這里就不部署了
http://www.lxweimin.com/p/6bafe568f103
部署CoreDNS
CoreDNS用于集群內(nèi)部Service名稱解析
kubectl apply -f coredns.yaml
kubectl get pods -n kube-system ##查看coredns的pod是否運行正常
NAME READY STATUS RESTARTS AGE
coredns-5ffbfd976d-rkcmt 1/1 Running 0 23s
kube-flannel-ds-amd64-2kmcm 1/1 Running 0 14m
kube-flannel-ds-amd64-p9tdp 1/1 Running 0 39m
kube-flannel-ds-amd64-zg7xz 1/1 Running 0 19m
測試
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
