kubeadm/flannel/dashboard/harbor部署以及服務發布
目錄
- kubeadm/flannel/dashboard/harbor部署以及服務發布
- 一、部署kubeadm
- 1. 服務器配置
- 2. 部署思路
- 3. 環境准備
- 4. 所有節點安裝docker
- 5.所有節點安裝kubeadm，kubelet和kubectl
- 6. 部署K8S集群
- 6.1 查看初始化需要的鏡像
- 6.2 在master節點上傳kubeadm基礎鏡像壓縮包至/opt目錄
- 6.3 解壓kubeadm基礎鏡像壓縮包
- 6.4 加載鏡像至docker容器
- 6.5 復制鏡像和腳本到node節點，並在node節點上執行“bash /opt/load-images.sh”
- 6.6 初始化kubeadm
- 6.7 設定kubectl
- 6.8 在node節點上執行kubeadm join命令加入群集
- 6.9 查看群集節點
- 6.10 所有節點部署網絡插件flannel
- 6.11 查看節點狀態
- 6.12 測試pod資源創建
- 6.13 暴露端口提供服務
- 6.14 測試訪問
- 6.15 擴展3個副本
- 二、安裝dashboard
- 三、 安裝Harbor私有倉庫
- 四、服務發布
- 補充：內核參數優化方案
- 一、部署kubeadm
一、部署kubeadm
1. 服務器配置
| 服務器（主機名） | 配置 | ip | 主要軟件 |
|---|---|---|---|
| master | 2C/4G，cpu核心數要求大於2 | 192.168.122.10 | docker/kubeadm/kubelet/kubectl/flannel |
| node01 | 2C2G | 192.168.122.11 | docker/kubeadm/kubelet/kubectl/flannel |
| node02 | 2C2G | 192.168.122.12 | docker/kubeadm/kubelet/kubectl/flannel |
| harbor | 2C2G | 192.168.122.13 | docker/docker-compose/harbor-office-v1.2.2 |
2. 部署思路
- 在所有節點上安裝Docker和kubeadm
- 部署Kubernetes Master
- 部署容器網絡插件
- 部署Kubernetes Node，將節點加入Kubernetes集群中
- 部署Dashboard Web頁面，可視化查看Kubernetes資源
- 部署Harbor私有倉庫，存放鏡像資源
3. 環境准備
3.1 關閉防火牆規則，關閉selinux
systemctl disable --now firewalld
setenforce 0
iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X
3.2 關閉swap
swapoff -a
#交換分區必須要關閉
sed -ri 's/.*swap.*/#&/' /etc/fstab
#永久關閉swap分區，&符號在sed命令中代表上次匹配的結果
3.3 加載ip_vs模塊
for i in $(ls /usr/lib/modules/$(uname -r)/kernel/net/netfilter/ipvs|grep -o "^[^.]*");do echo $i; /sbin/modinfo -F filename $i >/dev/null 2>&1 && /sbin/modprobe $i;done
#加載ip_vs模塊
3.4 修改主機名
hostnamectl set-hostname master
hostnamectl set-hostname node01
hostnamectl set-hostname node02
hostnamectl set-hostname harbor
3.5 所有節點修改hosts文件
cat >> /etc/hosts << EOF
192.168.122.10 master
192.168.122.11 node01
192.168.122.12 node02
192.168.122.13 hub.test.com
EOF
3.6 調整內核參數
cat > /etc/sysctl.d/kubernetes.conf << EOF
net.bridge.bridge-nf-call-ip6tables=1
net.bridge.bridge-nf-call-iptables=1
net.ipv6.conf.all.disable_ipv6=1
net.ipv4.ip_forward=1
EOF
sysctl --system
4. 所有節點安裝docker
4.1 安裝docker
yum install -y yum-utils device-mapper-persistent-data lvm2
yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
yum install -y docker-ce docker-ce-cli containerd.io
4.2 編寫daemon.json
mkdir /etc/docker
cat > /etc/docker/daemon.json <<EOF
{
"registry-mirrors": ["https://6ijb8ubo.mirror.aliyuncs.com"],
"exec-opts": ["native.cgroupdriver=systemd"],
"log-driver": "json-file",
"log-opts": {
"max-size": "100m"
}
}
EOF
使systemd管理Cgroup來進行資源控制與管理，因為相對cgoupfs而言，systemd限制CPU、內存等資源更加簡單和成熟穩定。
日志使用json-file格式類型存儲，大小為100M，保存在/var/log/containers目錄下，方便ELK等日志系統收集和管理日志。
4.3 啟動docker
systemctl daemon-reload
systemctl enable --now docker.service
4.4 查看Cgroup Driver
docker info | grep "Cgroup Driver"
Cgroup Driver: systemd
5.所有節點安裝kubeadm，kubelet和kubectl
5.1 定義kubernetes源
cat > /etc/yum.repos.d/kubernetes.repo << EOF
[kubernetes]
name=Kubernetes
baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=0
repo_gpgcheck=0
gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
EOF
5.2 安裝kubelet-1.15.1/kubeadm-1.15.1/kubectl-1.15.1
yum install -y kubelet-1.15.1 kubeadm-1.15.1 kubectl-1.15.1
5.3 啟動kubelet服務
systemctl enable kubelet.service
k8s通過kubeadm安裝出來以后都是以Pod方式存在，即底層是以容器方式運行，所以kubelet必須設置開機自啟。
6. 部署K8S集群
6.1 查看初始化需要的鏡像
[root@master ~]# kubeadm config images list
I1101 16:27:21.818586 2547 version.go:248] remote version is much newer: v1.22.3; falling back to: stable-1.15
k8s.gcr.io/kube-apiserver:v1.15.12
k8s.gcr.io/kube-controller-manager:v1.15.12
k8s.gcr.io/kube-scheduler:v1.15.12
k8s.gcr.io/kube-proxy:v1.15.12
k8s.gcr.io/pause:3.1
k8s.gcr.io/etcd:3.3.10
k8s.gcr.io/coredns:1.3.1
6.2 在master節點上傳kubeadm基礎鏡像壓縮包至/opt目錄
[root@master ~]# cd /opt
[root@master opt]# rz -E
rz waiting to receive.
#上傳kubeadm-basic.images.tar.gz壓縮包
6.3 解壓kubeadm基礎鏡像壓縮包
[root@master opt]# tar zxvf kubeadm-basic.images.tar.gz
kubeadm-basic.images/
kubeadm-basic.images/coredns.tar
kubeadm-basic.images/etcd.tar
kubeadm-basic.images/pause.tar
kubeadm-basic.images/apiserver.tar
kubeadm-basic.images/proxy.tar
kubeadm-basic.images/kubec-con-man.tar
kubeadm-basic.images/scheduler.tar
6.4 加載鏡像至docker容器
[root@master opt]# for i in $(ls /opt/kubeadm-basic.images/*.tar); do docker load -i $i; done
fe9a8b4f1dcc: Loading layer [==================================================>] 43.87MB/43.87MB
d1e1f61ac9f3: Loading layer [==================================================>] 164.5MB/164.5MB
Loaded image: k8s.gcr.io/kube-apiserver:v1.15.1
fb61a074724d: Loading layer [==================================================>] 479.7kB/479.7kB
c6a5fc8a3f01: Loading layer [==================================================>] 40.05MB/40.05MB
Loaded image: k8s.gcr.io/coredns:1.3.1
8a788232037e: Loading layer [==================================================>] 1.37MB/1.37MB
30796113fb51: Loading layer [==================================================>] 232MB/232MB
6fbfb277289f: Loading layer [==================================================>] 24.98MB/24.98MB
Loaded image: k8s.gcr.io/etcd:3.3.10
aa3154aa4a56: Loading layer [==================================================>] 116.4MB/116.4MB
Loaded image: k8s.gcr.io/kube-controller-manager:v1.15.1
e17133b79956: Loading layer [==================================================>] 744.4kB/744.4kB
Loaded image: k8s.gcr.io/pause:3.1
15c9248be8a9: Loading layer [==================================================>] 3.403MB/3.403MB
00bb677df982: Loading layer [==================================================>] 36.99MB/36.99MB
Loaded image: k8s.gcr.io/kube-proxy:v1.15.1
e8d95f5a4f50: Loading layer [==================================================>] 38.79MB/38.79MB
Loaded image: k8s.gcr.io/kube-scheduler:v1.15.1
[root@master opt]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
k8s.gcr.io/kube-controller-manager v1.15.1 d75082f1d121 2 years ago 159MB
k8s.gcr.io/kube-proxy v1.15.1 89a062da739d 2 years ago 82.4MB
k8s.gcr.io/kube-scheduler v1.15.1 b0b3c4c404da 2 years ago 81.1MB
k8s.gcr.io/kube-apiserver v1.15.1 68c3eb07bfc3 2 years ago 207MB
k8s.gcr.io/coredns 1.3.1 eb516548c180 2 years ago 40.3MB
k8s.gcr.io/etcd 3.3.10 2c4adeb21b4f 2 years ago 258MB
k8s.gcr.io/pause 3.1 da86e6ba6ca1 3 years ago 742kB
6.5 復制鏡像和腳本到node節點，並在node節點上執行“bash /opt/load-images.sh”
master
[root@master opt]# scp -r kubeadm-basic.images root@node01:/opt
The authenticity of host 'node01 (192.168.122.11)' can't be established.
ECDSA key fingerprint is SHA256:78ggzpsAbzvZM41OdKIGpmClMnNK/cxVQKDU4LFjbCA.
ECDSA key fingerprint is MD5:be:36:06:51:56:03:f8:0b:43:8b:a9:03:3c:91:aa:d5.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'node01,192.168.122.11' (ECDSA) to the list of known hosts.
root@node01's password:
coredns.tar 100% 39MB 110.3MB/s 00:00
etcd.tar 100% 246MB 139.3MB/s 00:01
pause.tar 100% 737KB 78.8MB/s 00:00
apiserver.tar 100% 199MB 134.1MB/s 00:01
proxy.tar 100% 80MB 129.3MB/s 00:00
kubec-con-man.tar 100% 153MB 167.5MB/s 00:00
scheduler.tar 100% 79MB 156.8MB/s 00:00
[root@master opt]# scp -r kubeadm-basic.images root@node02:/opt
The authenticity of host 'node02 (192.168.122.12)' can't be established.
ECDSA key fingerprint is SHA256:VZGGMMTK4KF/0n10SPQZ5+gjbPWA+2INFv05R3MSlog.
ECDSA key fingerprint is MD5:fa:3c:f3:ee:f1:b2:91:06:95:94:f2:94:04:d3:69:5c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'node02,192.168.122.12' (ECDSA) to the list of known hosts.
root@node02's password:
coredns.tar 100% 39MB 118.6MB/s 00:00
etcd.tar 100% 246MB 160.7MB/s 00:01
pause.tar 100% 737KB 99.7MB/s 00:00
apiserver.tar 100% 199MB 168.4MB/s 00:01
proxy.tar 100% 80MB 161.2MB/s 00:00
kubec-con-man.tar 100% 153MB 161.0MB/s 00:00
scheduler.tar 100% 79MB 152.9MB/s 00:00
node節點（以node01為例）
[root@node01 ~]# cd /opt
[root@node01 opt]# for i in $(ls /opt/kubeadm-basic.images/*.tar); do docker load -i $i; done
fe9a8b4f1dcc: Loading layer [==================================================>] 43.87MB/43.87MB
d1e1f61ac9f3: Loading layer [==================================================>] 164.5MB/164.5MB
Loaded image: k8s.gcr.io/kube-apiserver:v1.15.1
fb61a074724d: Loading layer [==================================================>] 479.7kB/479.7kB
c6a5fc8a3f01: Loading layer [==================================================>] 40.05MB/40.05MB
Loaded image: k8s.gcr.io/coredns:1.3.1
8a788232037e: Loading layer [==================================================>] 1.37MB/1.37MB
30796113fb51: Loading layer [==================================================>] 232MB/232MB
6fbfb277289f: Loading layer [==================================================>] 24.98MB/24.98MB
Loaded image: k8s.gcr.io/etcd:3.3.10
aa3154aa4a56: Loading layer [==================================================>] 116.4MB/116.4MB
Loaded image: k8s.gcr.io/kube-controller-manager:v1.15.1
e17133b79956: Loading layer [==================================================>] 744.4kB/744.4kB
Loaded image: k8s.gcr.io/pause:3.1
15c9248be8a9: Loading layer [==================================================>] 3.403MB/3.403MB
00bb677df982: Loading layer [==================================================>] 36.99MB/36.99MB
Loaded image: k8s.gcr.io/kube-proxy:v1.15.1
e8d95f5a4f50: Loading layer [==================================================>] 38.79MB/38.79MB
Loaded image: k8s.gcr.io/kube-scheduler:v1.15.1
6.6 初始化kubeadm
6.6.1 方法一
[root@master opt]# kubeadm config print init-defaults > /opt/kubeadm-config.yaml
[root@master opt]# cd /opt/
[root@master opt]# vim kubeadm-config.yaml
......
11 localAPIEndpoint:
12 advertiseAddress: 192.168.122.10 #指定master節點的IP地址
13 bindPort: 6443
......
34 kubernetesVersion: v1.15.1 #指定kubernetes版本號
35 networking:
36 dnsDomain: cluster.local
37 podSubnet: "10.244.0.0/16" #指定pod網段，10.244.0.0/16用於匹配flannel默認網段
38 serviceSubnet: 10.96.0.0/16 #指定service網段
39 scheduler: {}
--- #末尾再添加以下內容
apiVersion: kubeproxy.config.k8s.io/v1alpha1
kind: KubeProxyConfiguration
mode: ipvs #把默認的service調度方式改為ipvs模式
[root@master opt]# kubeadm init --config=kubeadm-config.yaml --experimental-upload-certs | tee kubeadm-init.log
#--experimental-upload-certs 參數可以在后續執行加入節點時自動分發證書文件，k8sV1.16版本開始替換為 --upload-certs
#tee kubeadm-init.log 用以輸出日志
......
kubeadm join 192.168.122.10:6443 --token abcdef.0123456789abcdef \
--discovery-token-ca-cert-hash sha256:c6af5fbc050fda97161487f525cc1b2f1b15e4a660910b5d8ba5598a5e937c7c
#注意記錄，node節點使用該命令加入集群
查看kubeadm-init日志
[root@master opt]# less kubeadm-init.log
kubernetes配置文件目錄
[root@master opt]# ls /etc/kubernetes/
admin.conf controller-manager.conf kubelet.conf manifests pki scheduler.conf
存放ca等證書和密碼的目錄
[root@master opt]# ls /etc/kubernetes/pki/
apiserver.crt apiserver.key ca.crt front-proxy-ca.crt front-proxy-client.key
apiserver-etcd-client.crt apiserver-kubelet-client.crt ca.key front-proxy-ca.key sa.key
apiserver-etcd-client.key apiserver-kubelet-client.key etcd front-proxy-client.crt sa.pub
6.6.2 方法二
[root@master opt]# kubeadm init \
> --apiserver-advertise-address=0.0.0.0 \
> --image-repository registry.aliyuncs.com/google_containers \
> --kubernetes-version=v1.15.1 \
> --service-cidr=10.1.0.0/16 \
> --pod-network-cidr=10.244.0.0/16
初始化集群需使用kubeadm init命令，可以指定具體參數初始化，也可以指定配置文件初始化。
可選參數：
--apiserver-advertise-address：apiserver通告給其他組件的IP地址，一般應該為Master節點的用於集群內部通信的IP地址，0.0.0.0表示節點上所有可用地址
--apiserver-bind-port：apiserver的監聽端口，默認是6443
--cert-dir：通訊的ssl證書文件，默認/etc/kubernetes/pki
--control-plane-endpoint：控制台平面的共享終端，可以是負載均衡的ip地址或者dns域名，高可用集群時需要添加
--image-repository：拉取鏡像的鏡像倉庫，默認是k8s.gcr.io
--kubernetes-version：指定kubernetes版本
--pod-network-cidr：pod資源的網段，需與pod網絡插件的值設置一致。通常，Flannel網絡插件的默認為10.244.0.0/16，Calico插件的默認值為192.168.0.0/16；
--service-cidr：service資源的網段
--service-dns-domain：service全域名的后綴，默認是cluster.local
注：
方法二初始化后需要修改 kube-proxy 的 configmap，開啟 ipvs
kubectl edit cm kube-proxy -n=kube-system
修改mode: ipvs
6.7 設定kubectl
kubectl需經由API server認證及授權后方能執行相應的管理操作，kubeadm 部署的集群為其生成了一個具有管理員權限的認證配置文件 /etc/kubernetes/admin.conf，它可由 kubectl 通過默認的 “$HOME/.kube/config” 的路徑進行加載。
[root@master opt]# mkdir -p $HOME/.kube
[root@master opt]# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@master opt]# sudo chown $(id -u):$(id -g) $HOME/.kube/config
[root@master opt]# cd
[root@master ~]# ls
anaconda-ks.cfg initial-setup-ks.cfg 公共 模板 視頻 圖片 文檔 下載 音樂 桌面
[root@master ~]# ls -A
anaconda-ks.cfg .bash_profile .config .esd_auth .kube .pki .viminfo .xauth5jhnq5 公共 圖片 音樂
.bash_history .bashrc .cshrc .ICEauthority .local .ssh .viminfo.tmp .xautheLhPWX 模板 文檔 桌面
.bash_logout .cache .dbus initial-setup-ks.cfg .mozilla .tcshrc .xauth0RM67K .Xauthority 視頻 下載
6.8 在node節點上執行kubeadm join命令加入群集
node節點（以node01為例）
[root@node01 opt]# kubeadm join 192.168.122.10:6443 --token abcdef.0123456789abcdef \
> --discovery-token-ca-cert-hash sha256:c6af5fbc050fda97161487f525cc1b2f1b15e4a660910b5d8ba5598a5e937c7c
6.9 查看群集節點
master節點
[root@master ~]# kubectl get node
NAME STATUS ROLES AGE VERSION
master NotReady master 35m v1.15.1
node01 NotReady <none> 26m v1.15.1
node02 NotReady <none> 26m v1.15.1
[root@master ~]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-5c98db65d4-2n6jb 0/1 Pending 0 36m
coredns-5c98db65d4-kc2ln 0/1 Pending 0 36m
etcd-master 1/1 Running 0 36m
kube-apiserver-master 1/1 Running 0 35m
kube-controller-manager-master 1/1 Running 0 35m
kube-proxy-9m4m2 1/1 Running 0 28m
kube-proxy-d8bp8 1/1 Running 0 28m
kube-proxy-dr4rl 1/1 Running 0 36m
kube-scheduler-master 1/1 Running 0 35m
由於coredns組件還未啟動，因此節點狀態都為NotReady，下一步安裝flannel即可啟動
6.10 所有節點部署網絡插件flannel
6.10.1 方法一
所有節點上傳flannel鏡像 flannel.tar 到 /opt 目錄，master節點上傳 kube-flannel.yml 文件
[root@master ~]# cd /opt
[root@master opt]# rz -E
rz waiting to receive.
#所有節點上傳flannel鏡像 flannel.tar 到 /opt 目錄
[root@master opt]# rz -E
rz waiting to receive.
#master節點上傳 kube-flannel.yml 文件
所有節點載入flannel鏡像
[root@master opt]# docker load < flannel.tar
7bff100f35cb: Loading layer [==================================================>] 4.672MB/4.672MB
5d3f68f6da8f: Loading layer [==================================================>] 9.526MB/9.526MB
9b48060f404d: Loading layer [==================================================>] 5.912MB/5.912MB
3f3a4ce2b719: Loading layer [==================================================>] 35.25MB/35.25MB
9ce0bb155166: Loading layer [==================================================>] 5.12kB/5.12kB
Loaded image: wl/flannel:v0.11.0-amd64
在master節點創建flannel資源
[root@master opt]# kubectl apply -f kube-flannel.yml
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
daemonset.extensions/kube-flannel-ds-amd64 created
daemonset.extensions/kube-flannel-ds-arm64 created
daemonset.extensions/kube-flannel-ds-arm created
daemonset.extensions/kube-flannel-ds-ppc64le created
daemonset.extensions/kube-flannel-ds-s390x created
6.10.2 方法二
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
6.11 查看節點狀態
[root@master opt]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
master Ready master 59m v1.15.1
node01 Ready <none> 50m v1.15.1
node02 Ready <none> 50m v1.15.1
[root@master opt]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-bccdc95cf-nj2g5 1/1 Running 0 10m
coredns-bccdc95cf-qrlbp 1/1 Running 0 10m
etcd-master 1/1 Running 0 9m35s
kube-apiserver-master 1/1 Running 0 9m55s
kube-controller-manager-master 1/1 Running 0 9m54s
kube-flannel-ds-amd64-6927f 1/1 Running 0 42s
kube-flannel-ds-amd64-mn4jn 1/1 Running 0 42s
kube-flannel-ds-amd64-p2sn9 1/1 Running 0 42s
kube-proxy-4f5hh 1/1 Running 0 9m25s
kube-proxy-7dk79 1/1 Running 0 10m
kube-proxy-hjqfc 1/1 Running 0 9m25s
kube-scheduler-master 1/1 Running 0 9m41s
6.12 測試pod資源創建
[root@master opt]# kubectl create deployment nginx --image=nginx
deployment.apps/nginx created
[root@master opt]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx-554b9c67f9-q6h77 1/1 Running 0 43s 10.244.1.3 node01 <none> <none>
6.13 暴露端口提供服務
[root@master opt]# kubectl expose deployment nginx --port=80 --type=NodePort
service/nginx exposed
6.14 測試訪問
[root@master opt]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.1.0.1 <none> 443/TCP 15m
nginx NodePort 10.1.81.149 <none> 80:30504/TCP 27s
[root@master opt]# curl http://node01:30504
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
6.15 擴展3個副本
[root@master opt]# kubectl scale deployment nginx --replicas=3
deployment.extensions/nginx scaled
[root@master opt]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx-554b9c67f9-6xp9g 1/1 Running 0 41s 10.244.2.3 node02 <none> <none>
nginx-554b9c67f9-q6h77 1/1 Running 0 4m36s 10.244.1.3 node01 <none> <none>
nginx-554b9c67f9-tzszr 1/1 Running 0 41s 10.244.1.4 node01 <none> <none>
二、安裝dashboard
1. 所有節點安裝dashboard
1.1 方法一
所有節點上傳dashboard鏡像 dashboard.tar 到 /opt 目錄，master節點上傳kubernetes-dashboard.yaml文件
[root@master ~]# cd /opt
[root@master opt]# rz -E
#所有節點上傳dashboard鏡像 dashboard.tar 到 /opt 目錄
rz waiting to receive.
[root@master opt]# rz -E
#master節點上傳kubernetes-dashboard.yaml文件
rz waiting to receive.
所有節點載入dashboard鏡像
[root@master opt]# docker load < dashboard.tar
master節點
[root@master opt]# kubectl apply -f kubernetes-dashboard.yaml
secret/kubernetes-dashboard-certs created
serviceaccount/kubernetes-dashboard created
role.rbac.authorization.k8s.io/kubernetes-dashboard-minimal created
rolebinding.rbac.authorization.k8s.io/kubernetes-dashboard-minimal created
deployment.apps/kubernetes-dashboard created
service/kubernetes-dashboard created
1.2 方法二
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0/aio/deploy/recommended.yaml
2. 查看所有容器運行狀態
[root@master opt]# kubectl get pods,svc -n kube-system -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
pod/coredns-bccdc95cf-nj2g5 1/1 Running 0 27m 10.244.2.2 node02 <none> <none>
pod/coredns-bccdc95cf-qrlbp 1/1 Running 0 27m 10.244.1.2 node01 <none> <none>
pod/etcd-master 1/1 Running 0 26m 192.168.122.10 master <none> <none>
pod/kube-apiserver-master 1/1 Running 0 26m 192.168.122.10 master <none> <none>
pod/kube-controller-manager-master 1/1 Running 0 26m 192.168.122.10 master <none> <none>
pod/kube-flannel-ds-amd64-6927f 1/1 Running 0 17m 192.168.122.11 node01 <none> <none>
pod/kube-flannel-ds-amd64-mn4jn 1/1 Running 0 17m 192.168.122.12 node02 <none> <none>
pod/kube-flannel-ds-amd64-p2sn9 1/1 Running 0 17m 192.168.122.10 master <none> <none>
pod/kube-proxy-4f5hh 1/1 Running 0 26m 192.168.122.12 node02 <none> <none>
pod/kube-proxy-7dk79 1/1 Running 0 27m 192.168.122.10 master <none> <none>
pod/kube-proxy-hjqfc 1/1 Running 0 26m 192.168.122.11 node01 <none> <none>
pod/kube-scheduler-master 1/1 Running 0 26m 192.168.122.10 master <none> <none>
pod/kubernetes-dashboard-859b87d4f7-rwdjf 1/1 Running 0 5m38s 10.244.2.4 node02 <none> <none>
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
service/kube-dns ClusterIP 10.1.0.10 <none> 53/UDP,53/TCP,9153/TCP 27m k8s-app=kube-dns
service/kubernetes-dashboard NodePort 10.1.46.39 <none> 443:30001/TCP 5m38s k8s-app=kubernetes-dashboard
3. 訪問測試
3.1 使用火狐或者360訪問
Edge和Chrome訪問方式詳見上篇博客
登錄需獲取令牌
3.2 令牌獲取
3.2.1 創建service account並綁定默認cluster-admin管理員集群角色
[root@master opt]# kubectl create serviceaccount dashboard-admin -n kube-system
serviceaccount/dashboard-admin created
[root@master opt]# kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin
clusterrolebinding.rbac.authorization.k8s.io/dashboard-admin created
3.2.2 獲取令牌密鑰
[root@master opt]# kubectl describe secrets -n kube-system $(kubectl -n kube-system get secret | awk '/dashboard-admin/{print $1}')
Name: dashboard-admin-token-ftm97
Namespace: kube-system
Labels: <none>
Annotations: kubernetes.io/service-account.name: dashboard-admin
kubernetes.io/service-account.uid: 9a5a16cf-73ad-44d5-ad86-14a8ca2daf76
Type: kubernetes.io/service-account-token
Data
====
ca.crt: 1025 bytes
namespace: 11 bytes
token: eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkYXNoYm9hcmQtYWRtaW4tdG9rZW4tZnRtOTciLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGFzaGJvYXJkLWFkbWluIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiOWE1YTE2Y2YtNzNhZC00NGQ1LWFkODYtMTRhOGNhMmRhZjc2Iiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmUtc3lzdGVtOmRhc2hib2FyZC1hZG1pbiJ9.FTzrxUPFyIMcFMmqUVlvIXsnfqxYxREhMIbdrNTr-VmN6K9JUSY7zM1eRxBcNiTu3nDkBGZRn2IVhvIT3-dWp5wckO0PFndfcI1lW3hxg-TUZ38DMnU4HdVPdQeJhiTUF95z5Y9cJLrCT_Ai9CXa6t8e-3Ln7_8u-xr1rQBr7NxhpgppXct57aDB9Vc_ijn04Qq9ITVRdgL8wDWnpmbrFozWYJCin0FGp63JuBwPWIMfy601yDo-LKr4_lexry9KWWsDWsZlfruglQaT8lhqgoQijqNq7OcYUsf3u3LnQDysbktc-nN_WRcewNlASSU3rsteDGs3QK2S5DRrSpX2Ag
復制token令牌
3.3 使用令牌登錄
三、 安裝Harbor私有倉庫
1. 安裝docker
[root@harbor ~]# yum install -y yum-utils device-mapper-persistent-data lvm2
[root@harbor ~]# yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
[root@harbor ~]# yum install -y docker-ce docker-ce-cli containerd.io
2. 編寫daemon.json
[root@harbor ~]# mkdir /etc/docker
[root@harbor ~]# cat > /etc/docker/daemon.json <<EOF
> {
> "registry-mirrors": ["https://6ijb8ubo.mirror.aliyuncs.com"],
> "exec-opts": ["native.cgroupdriver=systemd"],
> "log-driver": "json-file",
> "log-opts": {
> "max-size": "100m"
> },
> "insecure-registries": ["https://hub.test.com"]
> }
> EOF
3. 啟動docker
[root@harbor ~]# systemctl enable --now docker
Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
[root@harbor ~]# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: active (running) since 一 2021-11-01 19:56:40 CST; 8s ago
4. 所有node節點都修改docker配置文件，加上私有倉庫配置
node節點，以node01為例
[root@node01 opt]# cat > /etc/docker/daemon.json <<EOF
> {
> "registry-mirrors": ["https://6ijb8ubo.mirror.aliyuncs.com"],
> "exec-opts": ["native.cgroupdriver=systemd"],
> "log-driver": "json-file",
> "log-opts": {
> "max-size": "100m"
> },
> "insecure-registries": ["https://hub.test.com"]
> }
> EOF
[root@node01 opt]# systemctl daemon-reload
[root@node01 opt]# systemctl restart docker
5. 安裝Harbor
5.1 上傳 harbor-offline-installer-v1.2.2.tgz 和 docker-compose 文件到 /opt 目錄
[root@harbor ~]# cd /opt
[root@harbor opt]# rz -E
#上傳harbor-offline-installer-v1.2.2.tgz
rz waiting to receive.
[root@harbor opt]# rz -E
#上傳docker-compose
rz waiting to receive.
[root@harbor opt]# cp docker-compose /usr/local/bin/
[root@harbor opt]# chmod +x /usr/local/bin/docker-compose
5.2 解壓縮
[root@harbor opt]# tar zxvf harbor-offline-installer-v1.2.2.tgz
[root@harbor opt]# cd harbor/
[root@harbor harbor]# vim harbor.cfg
##第5行，修改主機域名
5 hostname = hub.test.com
##第9行，修改使用協議
9 ui_url_protocol = https
6. 生成證書
[root@harbor harbor]# mkdir -p /data/cert
[root@harbor harbor]# cd !$
cd /data/cert
[root@harbor cert]# openssl genrsa -des3 -out server.key 2048
#生成私鑰
Generating RSA private key, 2048 bit long modulus
............................................................................................................................+++
......................................................................+++
e is 65537 (0x10001)
Enter pass phrase for server.key:
#輸入兩遍密碼：123456
Verifying - Enter pass phrase for server.key:
生成證書簽名請求文件
[root@harbor cert]# openssl req -new -key server.key -out server.csr
Enter pass phrase for server.key:
##輸入私鑰密碼
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:CN
##輸入國家名
State or Province Name (full name) []:BJ
##輸入省名
Locality Name (eg, city) [Default City]:BJ
##輸入市名
Organization Name (eg, company) [Default Company Ltd]:TEST
##輸入組織名
Organizational Unit Name (eg, section) []:TEST
##輸入機構名
Common Name (eg, your name or your server's hostname) []:hub.test.com
##輸入域名
Email Address []:admin@test.com
##輸入管理員郵箱
Please enter the following 'extra' attributes
to be sent with your certificate request
##其他全部直接回車
A challenge password []:
An optional company name []:
7. 備份私鑰
[root@harbor cert]# ls
server.csr server.key
[root@harbor cert]# cp server.key server.key.org
[root@harbor cert]# ls
server.csr server.key server.key.org
8. 清除私鑰密碼
[root@harbor cert]# openssl rsa -in server.key.org -out server.key
Enter pass phrase for server.key.org:
writing RSA key
#輸入私鑰密碼：123456
9. 簽名證書
[root@harbor cert]# openssl x509 -req -days 1000 -in server.csr -signkey server.key -out server.crt
Signature ok
subject=/C=CN/ST=BJ/L=BJ/O=TEST/OU=TEST/CN=hub.test.com/emailAddress=admin@test.com
Getting Private key
[root@harbor cert]# chmod +x /data/cert/*
[root@harbor cert]# cd /opt/harbor/
[root@harbor harbor]# ./install.sh
10. 瀏覽器訪問https://hub.test.com
11. harbor倉庫操作
11.1 在一個node節點上登錄harbor
[root@node01 ~]# docker login -u admin -p Harbor12345 https://hub.test.com
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded
11.2 上傳鏡像
[root@node01 ~]# docker tag nginx:latest hub.test.com/library/nginx:v1
[root@node01 ~]# docker push hub.test.com/library/nginx:v1
The push refers to repository [hub.test.com/library/nginx]
9959a332cf6e: Pushed
f7e00b807643: Pushed
f8e880dfc4ef: Pushed
788e89a4d186: Pushed
43f4e41372e4: Pushed
e81bff2725db: Pushed
v1: digest: sha256:7250923ba3543110040462388756ef099331822c6172a050b12c7a38361ea46f size: 1570
11.3 在master節點上刪除之前創建的nginx資源
[root@master ~]# kubectl delete deployment nginx
deployment.extensions "nginx" deleted
[root@master ~]# kubectl get deploy
No resources found.
[root@master ~]# kubectl get all
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.1.0.1 <none> 443/TCP 19h
service/nginx NodePort 10.1.81.149 <none> 80:30504/TCP 19h
11.4 使用harbor倉庫鏡像
[root@master ~]# kubectl run nginx-deployment --image=hub.test.com/library/nginx:v1 --port=80 --replicas=3
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead.
deployment.apps/nginx-deployment created
[root@master ~]# kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-deployment-5477958d54-9wsvx 1/1 Running 0 66s
nginx-deployment-5477958d54-j4srm 1/1 Running 0 66s
nginx-deployment-5477958d54-xtnrz 1/1 Running 0 66s
四、服務發布
1. expose發布服務
[root@master ~]# kubectl expose deployment nginx-deployment --port=30000 --target-port=80
service/nginx-deployment exposed
[root@master ~]# kubectl get svc,pods
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.1.0.1 <none> 443/TCP 19h
service/nginx NodePort 10.1.81.149 <none> 80:30504/TCP 19h
service/nginx-deployment ClusterIP 10.1.180.65 <none> 30000/TCP 61s
NAME READY STATUS RESTARTS AGE
pod/nginx-deployment-5477958d54-9wsvx 1/1 Running 0 2m12s
pod/nginx-deployment-5477958d54-j4srm 1/1 Running 0 2m12s
pod/nginx-deployment-5477958d54-xtnrz 1/1 Running 0 2m12s
2. 訪問clusterip:port
10.1.180.65:30000
[root@master ~]# curl http://10.1.180.65:30000
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
3. 調度策略改為NodePort
[root@master ~]# kubectl edit svc nginx-deployment
##25行，修改為NodePort
type: NodePort
[root@master ~]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.1.0.1 <none> 443/TCP 19h
nginx NodePort 10.1.81.149 <none> 80:30504/TCP 19h
nginx-deployment NodePort 10.1.180.65 <none> 30000:32081/TCP 24m
4. 訪問測試
192.168.122.10:32081
[root@master ~]# curl 192.168.122.10:32081
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
192.168.122.11:32081
[root@master ~]# curl 192.168.122.11:32081
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
192.168.122.12:32081
[root@master ~]# curl 192.168.122.12:32081
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
補充：內核參數優化方案
cat > /etc/sysctl.d/kubernetes.conf <<EOF
net.bridge.bridge-nf-call-iptables=1
net.bridge.bridge-nf-call-ip6tables=1
net.ipv4.ip_forward=1
net.ipv4.tcp_tw_recycle=0
vm.swappiness=0
#禁止使用 swap 空間，只有當系統內存不足（OOM）時才允許使用它
vm.overcommit_memory=1
#不檢查物理內存是否夠用
vm.panic_on_oom=0
#開啟 OOM
fs.inotify.max_user_instances=8192
fs.inotify.max_user_watches=1048576
fs.file-max=52706963
#指定最大文件句柄數
fs.nr_open=52706963
#僅4.4以上版本支持
net.ipv6.conf.all.disable_ipv6=1
net.netfilter.nf_conntrack_max=2310720
EOF