一、k8s高可用的2中部署方式
1，一種是將etcd與Master節點組件混布在一起
2，另外一種方式是，使用獨立的Etcd集群，不與Master節點混布
通過kubeadm搭建一個高可用的k8s集群，kubeadm可以幫助我們快速的搭建k8s集群，高可用主要體現在對master節點組件及etcd存盤的高可用
二、環境準備
鑒于資源限制下面部署案例為2個master節點和1個node節點，在集群架構內環境擴展起來很方便
1、主機規劃
| 服務說明 | ip | 主機名規則 | 安裝服務 |
| maser01 | 192.168.109.111 | ha-maser01 | dashboard、kube-apiserver、kube-scheduler、kube-controller-manager、etcd、kubeadm、kubelet、kubectl |
| master02 | 192.168.109.111 | ha-master02 | kube-apiserver、kube-scheduler、kube-controller-manager、etcd、kubeadm、kubelet、kubectl |
| node01 | 192.168.109.111 | ha-node04 |
kubeadm,kubelet,kubectl |
2、部署docker
1、下載docker源wget https://download.docker.com/linux/centos/docker-ce.repo 并移動到/etc/yum.repos.d/目錄下面 mv docker-ce.repo /etc/yum.repos.d/
安裝docker服務并加入開機啟動
yum -y install docker-ce systemctl start docker && systemctl enable docker
2、使用官方安裝腳本自動安
命令：curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun
3、配置docker加速器并修改成k8s驅動
daemon.json檔案如果沒有自己創建
{ "exec-opts": ["native.cgroupdriver=systemd"], "log-driver": "json-file", "log-opts": { "max-size": "100m" }, "storage-driver": "overlay2", "storage-opts": [ "overlay2.override_kernel_check=true" ] }
重啟docker systemctl restart docker
4、更改各節點主機名
hostnamectl set-hostname 主機名
5、.配置各節點hosts檔案
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.109.111 ha-master01 192.168.109.112 ha-master02 192.168.109.114 ha-node04
6、關閉各個節點防火墻和SElinux
systemctl stop firewalld && systemctl disable firewalld
[root@ha01 ~]# cat /etc/sysconfig/selinux # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of three values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted
7、關閉每臺服務器swap磁區
[root@ha01 ~]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Mon Jan 11 22:49:08 2021 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/centos-root / xfs defaults 0 0 UUID=cb824a10-9132-4f88-b999-ea649de9cbba /boot xfs defaults 0 0 #/dev/mapper/centos-swap swap swap defaults 0 0
8、重啟服務reboot
9、同步每臺節點的時間 # 用chrony或者ntpdate都行
設定當前系統為Asia/Shanghai上海時區 timedatectl set-timezone Asia/Shanghai 設定完時區后，強制同步下系統時鐘： chronyc -a makestep
10、每臺服務器內核調整,將橋接的IPv4流量傳遞到iptables的鏈
[root@ha01 ~]# cat /etc/sysctl.d/k8s.conf net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 net.ipv4.ip_nonlocal_bind = 1 net.ipv4.ip_forward = 1
[root@ha01 ~]# sysctl -p /etc/sysctl.d/k8s.conf
11、配置每臺服務器增加k8s的yum源
[root@ha01 ~]# cat /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://mirrors.aliyun.com/kubernetes/yum/repos/kubernetes-el7-x86_64/ enabled=1 gpgcheck=1 repo_gpgcheck=1 gpgkey=https://mirrors.aliyun.com/kubernetes/yum/doc/yum-key.gpg https://mirrors.aliyun.com/kubernetes/yum/doc/rpm-package-key.gpg
12、每臺服務器安裝ipset服務
yum -y install ipvsadm ipset sysstat conntrack libseccomp
13、每臺服務器開啟ipvs模塊
[root@ha01 ~]# cat /etc/sysconfig/modules/ipvs.modules #!/bin/sh modprobe -- ip_vs modprobe -- ip_vs_rr modprobe -- ip_vs_wrr modprobe -- ip_vs_sh modprobe -- nf_conntrack_ipv4 [root@ha01 ~]# chmod 755 /etc/sysconfig/modules/ipvs.modules && bash /etc/sysconfig/modules/ipvs.modules && lsmod | grep -e ip_vs -e nf_conntrack_ipv4
三、master節點安裝haproxy和keepalived
1、安裝基本的依賴包
yum -y install net-tools vim lrzsz tree screen lsof tcpdump nc mtr nmap gcc glibc gcc-c++
2、創建記錄日志檔案
mkdir /var/log/haproxy
chmod a+w /var/log/haproxy
3、開啟rsyslog記錄haproxy日志功能
取消 /etc/rsyslog.conf檔案下面的如下2處
$ModLoad imudp
$UDPServerRun 514
在該檔案添加如下內容：
local3.* /var/log/haproxy/haproxy.log
4、修改“/etc/sysconfig/rsyslog”檔案
[root@ha01 ~]# cat /etc/sysconfig/rsyslog # Options for rsyslogd # Syslogd options are deprecated since rsyslog v3. # If you want to use them, switch to compatibility mode 2 by "-c 2" # See rsyslogd(8) for more details #SYSLOGD_OPTIONS="" SYSLOGD_OPTIONS="-r -m 0 -c 2"
5、重啟syslog服務
systemctl restart rsyslog.service
6，安裝keepalived、haproxy
yum -y install haproxy keepalived
7、修改keepalived主節點檔案
[root@ha01 ~]# cat /etc/sysconfig/rsyslog # Options for rsyslogd # Syslogd options are deprecated since rsyslog v3. # If you want to use them, switch to compatibility mode 2 by "-c 2" # See rsyslogd(8) for more details #SYSLOGD_OPTIONS="" SYSLOGD_OPTIONS="-r -m 0 -c 2" [root@ha01 ~]# cat /etc/keepalived/keepalived.conf ! Configuration File for keepalived global_defs { router_id LVS_DEVEL script_user root enable_script_security } vrrp_script check_haproxy { script "/etc/keepalived/check_haproxy.sh" # 檢測腳本路徑 interval 3 weight -2 fall 10 rise 2 } vrrp_instance VI_1 { state MASTER # 第一臺是MASTER，其他幾臺master是BACKUP interface ens33 # 本機網卡名 virtual_router_id 51 priority 100 # 權重后一臺要比前一臺小100，99，98 advert_int 1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 192.168.109.113 # 虛擬IP } track_script { check_haproxy # 模塊 } }
8、修改keepalived從節點檔案
[root@ha02 ~]# cat /etc/keepalived/keepalived.conf ! Configuration File for keepalived global_defs { router_id LVS_DEVEL script_user root enable_script_security } vrrp_script check_haproxy { script "/etc/keepalived/check_haproxy.sh" # 檢測腳本路徑 interval 3 weight -2 fall 10 rise 2 } vrrp_instance VI_1 { state BACKUP # 第一臺是MASTER，其他幾臺master是BACKUP interface ens33 # 本機網卡名 virtual_router_id 51 priority 99 # 權重后一臺要比前一臺小100，99，98 advert_int 1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 192.168.109.113 # 虛擬IP } track_script { check_haproxy # 模塊 } }
9、修改haproxy組態檔、多個節點配置一致
[root@ha02 ~]# cat /etc/haproxy/haproxy.cfg #--------------------------------------------------------------------- # Example configuration for a possible web application. See the # full configuration options online. # # http://haproxy.1wt.eu/download/1.4/doc/configuration.txt # #--------------------------------------------------------------------- #--------------------------------------------------------------------- # Global settings #--------------------------------------------------------------------- global # to have these messages end up in /var/log/haproxy.log you will # need to: # # 1) configure syslog to accept network log events. This is done # by adding the '-r' option to the SYSLOGD_OPTIONS in # /etc/sysconfig/syslog # # 2) configure local2 events to go to the /var/log/haproxy.log # file. A line like the following can be added to # /etc/sysconfig/syslog # # local2.* /var/log/haproxy.log # log 127.0.0.1 local3 info chroot /var/lib/haproxy pidfile /var/run/haproxy.pid maxconn 4000 user haproxy group haproxy daemon # turn on stats unix socket stats socket /var/lib/haproxy/stats #--------------------------------------------------------------------- # common defaults that all the 'listen' and 'backend' sections will # use if not designated in their block #--------------------------------------------------------------------- defaults mode http log global option httplog option dontlognull option http-server-close option forwardfor except 127.0.0.0/8 option redispatch retries 3 timeout http-request 10s timeout queue 1m timeout connect 10s timeout client 1m timeout server 1m timeout http-keep-alive 10s timeout check 10s maxconn 3000 #--------------------------------------------------------------------- # main frontend which proxys to the backends #--------------------------------------------------------------------- frontend kubernetes-apiserver mode tcp bind *:16443 option tcplog default_backend kubernetes-apiserver #--------------------------------------------------------------------- # static backend for serving up images, stylesheets and such #--------------------------------------------------------------------- listen stats mode http bind *:1080 stats auth admin:123456 stats refresh 30s #stats realm HAProxy\ Statistics stats uri /admin?stats #--------------------------------------------------------------------- # round robin balancing between the various backends #--------------------------------------------------------------------- backend kubernetes-apiserver mode tcp balance roundrobin server ha01 192.168.109.111:6443 check inter 2000 rise 30 fall 15 server ha02 192.168.109.112:6443 check inter 2000 rise 30 fall 15
10、每臺kubernetes-master節點撰寫健康監測腳本并賦予執行權限
[root@ha02 ~]# cat /etc/keepalived/check_haproxy.sh #!/bin/sh # HAPROXY down A=`ps -C haproxy --no-header | wc -l` if [ $A -eq 0 ] then systmectl start haproxy if [ ps -C haproxy --no-header | wc -l -eq 0 ] then killall -9 haproxy echo "HAPROXY down" | mail -s "haproxy" sleep 3600 fi fi
[root@ha02 ~]# chmod +x check_haproxy.sh
11、啟動keepalive和haproxy服務
systemctl start keepalived && systemctl enable keepalived
systemctl start haproxy && systemctl enable haproxy
12、查看keepalive的vip地址，只能在keepalived的master節點才有vip地址，當master節點keepalived服務結束vip會自動切到從節點
[root@ha01 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:0c:29:45:77:73 brd ff:ff:ff:ff:ff:ff inet 192.168.109.111/24 brd 192.168.109.255 scope global noprefixroute ens33 valid_lft forever preferred_lft forever inet 192.168.109.113/32 scope global ens33 valid_lft forever preferred_lft forever inet6 fe80::5599:adbd:dc2d:70b8/64 scope link noprefixroute valid_lft forever preferred_lft forever
13、驗證haproxy
瀏覽器輸入http://192.168.109.113:1080/admin?stats
輸入用戶名：admin，密碼：123456，如果出現如下資訊說明haproxy已經成功啟動了
四、部署kubernetes集群
1、每個節點安裝kubeadm,kubelet和kubectl # 安裝的kubeadm、kubectl和kubelet要和kubernetes版本一致，
kubelet加入開機啟動之后不手動啟動，要不然會報錯，初始化集群之后集群會自動啟動kubelet服務！！
yum -y install kubeadm-1.18.2 kubelet-1.18.2 kubectl-1.18.2
systemctl enable kubelet && systemctl daemon-reload
2、獲取默認組態檔kubeadm默認組態檔kubeadm-config.yaml
kubeadm config print init-defaults > kubeadm-config.yaml
3、修改組態檔kubeadm-config.yaml
由于默認拉取鏡像地址k8s.gcr.io國內無法訪問，這里指定阿里云鏡像倉庫地址：registry.aliyuncs.com/google_containers
[root@ha01 ~]# cat kubeadm-config.yaml apiVersion: kubeadm.k8s.io/v1beta2 bootstrapTokens: - groups: - system:bootstrappers:kubeadm:default-node-token token: abcdef.0123456789abcdef ttl: 24h0m0s usages: - signing - authentication kind: InitConfiguration localAPIEndpoint: advertiseAddress: 192.168.109.111 #本機地址 bindPort: 6443 #haproxy監聽埠 nodeRegistration: criSocket: /var/run/dockershim.sock name: ha01 taints: - effect: NoSchedule key: node-role.kubernetes.io/master --- apiServer: timeoutForControlPlane: 4m0s apiVersion: kubeadm.k8s.io/v1beta2 certificatesDir: /etc/kubernetes/pki clusterName: kubernetes controlPlaneEndpoint: "192.168.109.113:16443" #vip地址 controllerManager: {} dns: type: CoreDNS etcd: local: dataDir: /var/lib/etcd imageRepository: registry.aliyuncs.com/google_containers kind: ClusterConfiguration kubernetesVersion: v1.18.0 networking: dnsDomain: cluster.local podSubnet: "10.244.0.0/16" #新增一行 serviceSubnet: 10.96.0.0/12 scheduler: {} --- apiVersion: kubeproxy.config.k8s.io/v1alpha1 kind: KubeProxyConfiguration featureGates: SupportIPVSProxyMode: true mode: ipvs
4、下載集群相關鏡像
kubeadm config images pull --config kubeadm-config.yaml
5、鏡像串列如下
[root@ha01 ~]# docker images REPOSITORY TAG IMAGE ID CREATED SIZE kubernetesui/metrics-scraper v1.0.6 48d79e554db6 2 months ago 34.5MB registry.aliyuncs.com/google_containers/kube-proxy v1.18.0 43940c34f24f 9 months ago 117MB registry.aliyuncs.com/google_containers/kube-apiserver v1.18.0 74060cea7f70 9 months ago 173MB registry.aliyuncs.com/google_containers/kube-controller-manager v1.18.0 d3e55153f52f 9 months ago 162MB registry.aliyuncs.com/google_containers/kube-scheduler v1.18.0 a31f78c7c8ce 9 months ago 95.3MB registry.aliyuncs.com/google_containers/pause 3.2 80d28bedfe5d 11 months ago 683kB registry.aliyuncs.com/google_containers/coredns 1.6.7 67da37a9a360 11 months ago 43.8MB registry.aliyuncs.com/google_containers/etcd 3.4.3-0 303ce5db0e90 14 months ago 288MB
6、初始化集群
kubeadm init --config kubeadm-config.yaml
7、出現下面日志記錄表示集群初始化成功
You can now join any number of control-plane nodes by copying certificate authorities and service account keys on each node and then running the following as root: kubeadm join 192.168.109.113:16443 --token abcdef.0123456789abcdef \ --discovery-token-ca-cert-hash sha256:42c7804e1a7fcc33dafd967d35ffb9328c3c0045c726c50bea4118051f4c05e6 \ --control-plane Then you can join any number of worker nodes by running the following on each as root: kubeadm join 192.168.109.113:16443 --token abcdef.0123456789abcdef \ --discovery-token-ca-cert-hash sha256:42c7804e1a7fcc33dafd967d35ffb9328c3c0045c726c50bea4118051f4c05e6
8、在其它kubernete-master節點創建以下目錄
mkdir -p /etc/kubernetes/pki/etcd
9、把主master節點證書分別復制到其它master節點
scp /etc/kubernetes/pki/ca.* [email protected]:/etc/kubernetes/pki/ scp /etc/kubernetes/pki/sa.* [email protected]:/etc/kubernetes/pki/ scp /etc/kubernetes/pki/front-proxy-ca.* [email protected]:/etc/kubernetes/pki/ scp /etc/kubernetes/pki/etcd/ca.* [email protected]:/etc/kubernetes/pki/ scp /etc/kubernetes/pki/etcd/ca.* [email protected]:/etc/kubernetes/pki/etcd/ scp /etc/kubernetes/admin.conf [email protected]:/etc/kubernetes/
10、把主節點admin.conf證書復制到其他node節點
scp /etc/kubernetes/admin.conf [email protected]:/etc/kubernetes/
11、安裝網路插件，容器正常啟動起來時間可能需要5分鐘左右耐心等候
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
12、在主master節點外的其他master節點執行以下命令，該命令執行會自動同步k8s集群相關鏡像檔案
kubeadm join 192.168.109.113:16443 --token abcdef.0123456789abcdef \ --discovery-token-ca-cert-hash sha256:42c7804e1a7fcc33dafd967d35ffb9328c3c0045c726c50bea4118051f4c05e6 \ --control-plane
13、在所有node節點執行以下命令，該命令執行會自動同步k8s集群相關鏡像檔案
（2-7步只需要在主master節點執行就可以）
kubeadm join 192.168.109.113:16443 --token abcdef.0123456789abcdef \
--discovery-token-ca-cert-hash sha256:42c7804e1a7fcc33dafd967d35ffb9328c3c0045c726c50bea4118051f4c05e6
14、在所有節點執行以下命令
mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
15、查看集群狀態
[root@ha01 ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION ha01 Ready master 18h v1.18.2 ha02 Ready master 17h v1.18.2 ha04 Ready <none> 16h v1.18.2
16、查看pod運行狀態
[root@ha02 ~]# kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-7ff77c879f-dh82p 1/1 Running 0 18h kube-system coredns-7ff77c879f-wlhnl 1/1 Running 0 18h kube-system etcd-ha01 1/1 Running 7 18h kube-system etcd-ha02 1/1 Running 1 17h kube-system kube-apiserver-ha01 1/1 Running 8 18h kube-system kube-apiserver-ha02 1/1 Running 3 17h kube-system kube-controller-manager-ha01 1/1 Running 2 18h kube-system kube-controller-manager-ha02 1/1 Running 0 17h kube-system kube-flannel-ds-amd64-4dbd2 1/1 Running 0 17h kube-system kube-flannel-ds-amd64-6cvd2 1/1 Running 0 16h kube-system kube-flannel-ds-amd64-wrg4p 1/1 Running 0 18h kube-system kube-proxy-6hrq5 1/1 Running 0 18h kube-system kube-proxy-d6jc9 1/1 Running 0 16h kube-system kube-proxy-lkcpq 1/1 Running 0 17h kube-system kube-scheduler-ha01 1/1 Running 1 18h kube-system kube-scheduler-ha02 1/1 Running 1 17h
五、安裝dashboard
1、下載初始化檔案
wget https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0/aio/deploy/recommended.yaml
2，修改recommended.yaml ----只展示需要修改的部分內容
--- kind: Service apiVersion: v1 metadata: labels: k8s-app: kubernetes-dashboard name: kubernetes-dashboard namespace: kubernetes-dashboard spec: type: NodePort #增加NodePort ports: - port: 443 targetPort: 8443 nodePort: 30000 #增加映射到容器外埠 selector: k8s-app: kubernetes-dashboard
3、創建證書
mkdir dashboard-certs cd dashboard-certs # 創建命名空間 kubectl create namespace kubernetes-dashboard # 創建key檔案 openssl genrsa -out dashboard.key 2048 # 證書請求 openssl req -days 36000 -new -out dashboard.csr -key dashboard.key -subj '/CN=dashboard-cert' # 自簽證書 openssl x509 -req -in dashboard.csr -signkey dashboard.key -out dashboard.crt # 創建kubernetes-dashboard-certs物件 kubectl create secret generic kubernetes-dashboard-certs --from-file=dashboard.key --from-file=dashboard.crt -n kubernetes-dashboard
4，查看證書檔案
[root@ha01 ~]# ll dashboard-certs/ 總用量 12 -rw-r--r-- 1 root root 989 1月 12 15:50 dashboard.crt -rw-r--r-- 1 root root 899 1月 12 15:49 dashboard.csr -rw-r--r-- 1 root root 1675 1月 12 15:49 dashboard.key
5、運行recommended.yaml
kubectl create -f recommended.yaml #注意會報錯 Error from server (AlreadyExists): error when creating "./recommended.yaml": namespaces "kubernetes-dashboard" already exists #這是因為我們在創建證書時，已經創建了kubernetes-dashboard命名空間，所以，直接忽略此錯誤資訊即可，
6、查看安裝結果
[root@ha01 ~]# kubectl get pods -A -o wide | grep dashboard kubernetes-dashboard dashboard-metrics-scraper-78f5d9f487-qbqgr 1/1 Running 0 18h 10.244.0.12 ha01 <none> <none> kubernetes-dashboard kubernetes-dashboard-59ddbcfdcb-h7gsd 1/1 Running 8 18h 10.244.0.11 ha01 <none> <none>
7、查看暴露埠
[root@ha01 ~]# kubectl get service -n kubernetes-dashboard -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR dashboard-metrics-scraper ClusterIP 10.106.77.109 <none> 8000/TCP 18h k8s-app=dashboard-metrics-scraper kubernetes-dashboard NodePort 10.101.143.170 <none> 443:30000/TCP 18h k8s-app=kubernetes-dashboard
8、創建dashboard管理員
[root@ha01 ~]# cat dashboard-admin.yaml apiVersion: v1 kind: ServiceAccount metadata: labels: k8s-app: kubernetes-dashboard name: dashboard-admin namespace: kubernetes-dashboard
9、執行創建命令
kubectl create -f dashboard-admin.yaml
10、用戶權限分配
[root@ha01 ~]# cat dashboard-admin-bind-cluster-role.yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: dashboard-admin-bind-cluster-role labels: k8s-app: kubernetes-dashboard roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: dashboard-admin namespace: kubernetes-dashboard
11，執行分配命令
kubectl create -f dashboard-admin-bind-cluster-role.yaml
12、查看并復制用戶Token
[root@ha01 ~]# kubectl -n kubernetes-dashboard describe secret $(kubectl -n kubernetes-dashboard get secret | grep dashboard-admin | awk '{print $1}') Name: dashboard-admin-token-6ll6p Namespace: kubernetes-dashboard Labels: <none> Annotations: kubernetes.io/service-account.name: dashboard-admin kubernetes.io/service-account.uid: 4d358094-69b3-417a-85ea-241868f31957 Type: kubernetes.io/service-account-token Data ==== ca.crt: 1025 bytes namespace: 20 bytes token: eyJhbGciOiJSUzI1NiIsImtpZCI6IlA2WnBRZENRTEhVeUYzNFZJbGtLQTdpeXBTOF9fYnA2MHBKZExKNXpZdHMifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkYXNoYm9hcmQtYWRtaW4tdG9rZW4tNmxsNnAiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiZGFzaGJvYXJkLWFkbWluIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiNGQzNTgwOTQtNjliMy00MTdhLTg1ZWEtMjQxODY4ZjMxOTU3Iiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmVybmV0ZXMtZGFzaGJvYXJkOmRhc2hib2FyZC1hZG1pbiJ9.e3SUQTnthXX0VnH9_mXnaPZF4Q3xGeoiIhlYCVDzKd80T4zsLuPIn
13、查看dashboard界面
在瀏覽器中輸入鏈接https://192.168.109.113:30000/#/login 界面如下圖所示
14、我們選擇Token方式登錄，并輸入在命令列獲取到的Token，如下所示
15、登錄后進入dashboard，如下所示
注：該文章部分內容借鑒和參考https://www.cnblogs.com/lfl17718347843/p/13417304.html感謝大佬
轉載請註明出處，本文鏈接：https://www.uj5u.com/qita/253427.html
標籤：其他
上一篇：世上最可愛的人生謊言
下一篇：2021寒假每日一題《合唱隊形》