使用 kubeadm 部署 kubernetes 1.14.2 集群

之前在研究spring cloud Data Flow時有部署過 kubernetes，不過使用的是minikube搭建的，正好這幾天在極客時間學(xué)習(xí)《深入剖析 kubernetes》專欄，依據(jù)專欄里的搭建步驟和網(wǎng)上的相關(guān)教程搭建了1.14.2版本的集群。

環(huán)境規(guī)劃

由于沒有足夠的云主機(jī)，我在本地使用虛擬機(jī)搭建的，具體各個節(jié)點的配置如下：

IP地址 系統(tǒng)版本 內(nèi)存 角色
10.211.55.8 CentOS 7.6 4GB Master(主節(jié)點)
10.211.55.9 CentOS 7.6 4GB Worker(從節(jié)點)

每個節(jié)點需要安裝的軟件及版本如下：

軟件名稱 版本 說明
Docker 18.09.6 負(fù)責(zé)創(chuàng)建、拉取容器
kubeadm 1.14.2-0 負(fù)責(zé)初始化k8s集群
kubelet 1.14.2-0 運(yùn)行在所有節(jié)點上，負(fù)責(zé)啟動容器和Pod
kubectl 1.14.2-0 k8s命令行工具，負(fù)責(zé)與k8s集群交互，例如部署應(yīng)用

環(huán)境準(zhǔn)備

使用Vmware或其他虛擬機(jī)管理工具安裝兩臺CentOS7.6的步驟這里就不介紹了，下面是為了保證我們能正常使用kubeadm啟動kubernetes所需要做到前提工作。

系統(tǒng)配置

為了方便之后能快速辨識哪臺主機(jī)是什么類型的節(jié)點，我們需要為每臺主機(jī)設(shè)置代表其節(jié)點身份主機(jī)名，具體如下：

# 為 10.211.55.8 主節(jié)點設(shè)置主機(jī)名
hostnamectl --static set-hostname  master
# 為 10.211.55.9 從節(jié)點設(shè)置主機(jī)名
hostnamectl --static set-hostname  worker

另外還需要在每臺主機(jī)/etc/hosts文件中加上解析配置

vim /etc/hosts
#寫入如下類型，IP根據(jù)自己實際情況修改

10.211.55.8 master
10.211.55.9 worker

如果各個主機(jī)啟用了防火墻，則我們需要開放kubernetes各個組件所需要的端口，這里搭建是測試環(huán)境，只需要禁用各個節(jié)點的防火墻即可：

# 注意以下命令是下次生效
systemctl disable firewalld.service
systemctl stop firewalld.service

# 關(guān)閉防火墻立即生效
iptables -F

# 防火墻關(guān)閉后可以使用以下命令查看防火墻狀態(tài)
systemctl status firewalld

禁用SELINUX(它是一個 Linux 內(nèi)核模塊，也是 Linux 的一個安全子系統(tǒng))

##設(shè)置SELinux 成為permissive模式（不用重啟機(jī)器）
setenforce 0

# 修改配置文件 (重啟機(jī)器生效)
vim /etc/selinux/config
SELINUX=disabled

關(guān)閉Swap分區(qū)

swapoff -a

修改 /etc/fstab 文件，注釋掉 SWAP 的自動掛載，使用free -m確認(rèn)Swap已經(jīng)關(guān)閉。

創(chuàng)建/etc/sysctl.d/k8s.conf文件，添加如下內(nèi)容：

# 配置路由
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
# swappiness 參數(shù)設(shè)為 0 
vm.swappiness=0

執(zhí)行下面命令使修改生效

modprobe br_netfilter
sysctl -p /etc/sysctl.d/k8s.conf

軟件安裝

安裝Docker。這里安裝步驟完成依據(jù)官網(wǎng),可以參考官網(wǎng)了解更多

  • 如果之前安裝過，卸載舊版本

    sudo yum remove docker \
                  docker-client \
                  docker-client-latest \
                  docker-common \
                  docker-latest \
                  docker-latest-logrotate \
                  docker-logrotate \
                  docker-engine

  • 安裝所需的包

    sudo yum install -y yum-utils \
  device-mapper-persistent-data \
  lvm2

  • 設(shè)置穩(wěn)定版本（stable）存儲庫

    sudo yum-config-manager \
    --add-repo \
    https://download.docker.com/linux/centos/docker-ce.repo

  • 由于kubernetes 1.4支持的Docker版本最高為18.09,所以這里我們安裝的Docker版本為18.09.7

    sudo yum install docker-ce-18.09.7 docker-ce-cli-18.09.7 containerd.io

  • 啟動Docker和設(shè)置開機(jī)自啟

    systemctl start docker
systemctl enable docker

  • 修改docker cgroup driver為systemd

    vim /etc/docker/daemon.json
# 寫入如下內(nèi)容
{
  "exec-opts": ["native.cgroupdriver=systemd"]
}

  • 重啟Docker

    systemctl restart docker

安裝kubeadm、kubectl、kubelet三個組件

  • 安裝之前我們需要先添加yum源，命令如下：

    cat <<EOF > /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
EOF

  • 接著使用如下命令安裝1.14.2版本的各個組件

    yum install -y kubelet-1.14.2 kubeadm-1.14.2 kubectl-1.14.2

鏡像拉取

由于k8s的許多鏡像如果我們直接下是下載不下來的，所以我們需要想辦法先將集群所需的所有鏡像都下載好。好在阿里云提供了鏡像文件，我們只需要執(zhí)行下面命令即可

  • 拉取所需鏡像文件

    docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.14.2
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.14.2
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.14.2
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.14.2
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.3.10
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.3.1
docker pull registry.cn-shenzhen.aliyuncs.com/cp_m/flannel:v0.10.0-amd64
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kubernetes-dashboard-amd64:v1.10.1

  • 給鏡像打標(biāo)簽

    docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.14.2 k8s.gcr.io/kube-apiserver:v1.14.2
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.14.2 k8s.gcr.io/kube-controller-manager:v1.14.2
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.14.2 k8s.gcr.io/kube-scheduler:v1.14.2
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.14.2 k8s.gcr.io/kube-proxy:v1.14.2
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1 k8s.gcr.io/pause:3.1
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.3.10 k8s.gcr.io/etcd:3.3.10
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.3.1 k8s.gcr.io/coredns:1.3.1
docker tag registry.cn-shenzhen.aliyuncs.com/cp_m/flannel:v0.10.0-amd64 quay.io/coreos/flannel:v0.10.0-amd64
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/kubernetes-dashboard-amd64:v1.10.1 k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1

  • 刪除拉取的初始鏡像，只留打上標(biāo)簽的鏡像

    docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver:v1.14.2           
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager:v1.14.2  
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.14.2          
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy:v1.14.2               
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/pause:3.1                        
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/etcd:3.3.10                      
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/coredns:1.3.1
docker rmi registry.cn-shenzhen.aliyuncs.com/cp_m/flannel:v0.10.0-amd64
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/kubernetes-dashboard-amd64:v1.10.1

    上面步驟執(zhí)行完成之后，我們使用docker images命令就能看到所有鏡像了，顯示如下

    [root@Node1 ~]# docker images
REPOSITORY                              TAG                 IMAGE ID            CREATED             SIZE
k8s.gcr.io/kube-proxy                   v1.14.2             5c24210246bb        10 months ago       82.1MB
k8s.gcr.io/kube-apiserver               v1.14.2             5eeff402b659        10 months ago       210MB
k8s.gcr.io/kube-controller-manager      v1.14.2             8be94bdae139        10 months ago       158MB
k8s.gcr.io/kube-scheduler               v1.14.2             ee18f350636d        10 months ago       81.6MB
k8s.gcr.io/coredns                      1.3.1               eb516548c180        14 months ago       40.3MB
k8s.gcr.io/kubernetes-dashboard-amd64   v1.10.1             f9aed6605b81        15 months ago       122MB
k8s.gcr.io/etcd                         3.3.10              2c4adeb21b4f        16 months ago       258MB
quay.io/coreos/flannel                  v0.10.0-amd64       f0fad859c909        2 years ago         44.6MB
k8s.gcr.io/pause

安裝配置Kubernetes集群

Master 節(jié)點初始化

我們使用如下命令來初始化kubernetes

# --kubernetes-version=v1.14.2 指定安裝的k8s版本
# --apiserver-advertise-address 指定 Master 節(jié)點的 advertise address，也就是 IP 地址
# --pod-network-cidr 用于指定Pod的網(wǎng)絡(luò)范圍，下面采用的是flannel方案（https://github.com/coreos/flannel/blob/master/Documentation/kubernetes.md）
kubeadm init --kubernetes-version=v1.14.2 --apiserver-advertise-address 10.211.55.8 --pod-network-cidr=10.244.0.0/16

執(zhí)行之后，會有如下輸出

[init] Using Kubernetes version: v1.14.2
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Activating the kubelet service
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [master localhost] and IPs [10.211.55.8 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [master localhost] and IPs [10.211.55.8 127.0.0.1 ::1]
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.211.55.8]
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 16.501690 seconds
[upload-config] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.14" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --experimental-upload-certs
[mark-control-plane] Marking the node k8s-master as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node k8s-master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: y6awgp.6bvxt8l3rie2du5s
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] creating the "cluster-info" ConfigMap in the "kube-public" namespace
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 10.211.55.8:6443 --token br6a7j.79aimgudzio73jy5 \
    --discovery-token-ca-cert-hash sha256:0623e22780c5a25138208fc417f874a0c70ca28543acf52be52ee445ec0c1dd3

我們使用如下命令來配置kubectl

# root 模式下導(dǎo)入環(huán)境變量
export KUBECONFIG=/etc/kubernetes/admin.conf

# 重啟 kubelet
systemctl restart kubelet

添加連接集群的 config 配置

正如初始化之后打印出來的命令，我們需要執(zhí)行下面命令操作:

mkdir -p $HOME/.kube
cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
chown $(id -u):$(id -g) $HOME/.kube/config

安裝 flannel 網(wǎng)絡(luò)插件

我們可以使用如下命令來安裝。如果wget下載kube-flannel.yml失敗了，建議到瀏覽器下載好之后再試

wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

kubectl apply -f kube-flannel.yml

安裝完成之后，我們可以使用kubectl get pods -o wide --all-namespaces來查看目前集群中的所有pod信息；使用kubectl get node來查看目前集群中的節(jié)點信息，例如：

[root@Node1 ~]# kubectl get node
NAME    STATUS   ROLES    AGE    VERSION
master   Ready    master   7d1h   v1.14.2

Worker 節(jié)點加入集群

注意，Worker節(jié)點需要安裝配置環(huán)境準(zhǔn)備里的所有內(nèi)容。

其他節(jié)點加入集群的方式在集群初始化之后最后也打印出來了，如果我們忘記了或找不到了，可以在Master節(jié)點使用如下命令來獲取 join token

kubeadm token create --print-join-command

執(zhí)行完成之后打印如下類似信息：

kubeadm join 10.211.55.8:6443 --token e6gc7z.t52g39w7mxww18gn \
    --discovery-token-ca-cert-hash sha256:603fbd109caf000c0cffe286c7b2eeebaf88d0540e1ea226d7f1b239d0695f1e

[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config filewith 'kubectl -n kube-system get cm kubeadm-config -oyaml'
[kubeelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.14" ConfigMap in the kube-system namespace
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Activating the kubelet service
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

于是我們就可以再Worker節(jié)點執(zhí)行如下命令來加入到集群之中

# 基礎(chǔ)命令示例 kubeadm join --token <token> <master-ip>:<master-port> --discovery-token-ca-cert-hash sha256:<hash>

kubeadm join 10.211.55.8:6443 --token e6gc7z.t52g39w7mxww18gn \
    --discovery-token-ca-cert-hash sha256:603fbd109caf000c0cffe286c7b2eeebaf88d0540e1ea226d7f1b239d0695f1e

加入之后，我們就可以使用kubectl get node -o wide來查看集群節(jié)點的狀態(tài)信息

[root@Node1 ~]# kubectl get node -o wide
NAME    STATUS   ROLES    AGE    VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION           CONTAINER-RUNTIME
node1   Ready    master   7d1h   v1.14.2   10.211.55.8   <none>        CentOS Linux 7 (Core)   3.10.0-1062.el7.x86_64   docker://18.9.7
node2   Ready    <none>   7d1h   v1.14.2   10.211.55.9   <none>        CentOS Linux 7 (Core)   3.10.0-1062.el7.x86_64   docker://18.9.7

到這里，一個具有兩個節(jié)點的kubernetes集群就搭建好了。

集群重置或刪除

如果想要重置或刪除集群，我們可以結(jié)合下面幾個命令來實現(xiàn)

  • 刪除子節(jié)點

    # 查詢k8s集群所以節(jié)點
kubectl get nodes

# 刪除子節(jié)點 ，<node name> 代表子節(jié)點名稱
kubectl drain <node name> --delete-local-data --force --ignore-daemonsets
kubectl delete node <node name>

  • 重置節(jié)點

    # 主節(jié)點和子節(jié)點都能使用該命令重置
kubeadm reset

# 如果想要刪除節(jié)點上的集群文件，可以使用如下命令
rm -f $HOME/.kube/

安裝配置 Dashborad

安裝 Dashborad

Kubernetes Dashborad是一個集群可視化管理工具，我們在上面的鏡像拉取中已經(jīng)拉取了鏡像，現(xiàn)在我們需要在集群中安裝Dashborad。

先使用如下命令下載YAML配置文件

wget https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml

為了實現(xiàn)外網(wǎng)訪問，我們首先需要使用vim kubernetes-dashboard.yaml來編輯下載的YAML文件，在Service控制器中添加NodePort類型，具體內(nèi)容如下：

# ------------------- Dashboard Service ------------------- #

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

編輯完成之后，保存退出，然后使用下面命令來創(chuàng)建kubernetes-dashborad

kubectl apply -f kubernetes-dashboard.yaml

完成之后，我們就可以使用如下命令來查看dashborad的狀態(tài)和service端口

[root@Node1 ~]# kubectl get service -n kube-system
NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
kube-dns               ClusterIP   10.96.0.10      <none>        53/UDP,53/TCP,9153/TCP   7d2h
kubernetes-dashboard   NodePort    10.102.72.239   <none>        443:31234/TCP            7d
[root@Node1 ~]# kubectl get pods -n kube-system
NAME                                    READY   STATUS    RESTARTS   AGE
coredns-fb8b8dccf-pdq9j                 1/1     Running   1          7d2h
coredns-fb8b8dccf-pj6lk                 1/1     Running   1          7d2h
etcd-node1                              1/1     Running   1          7d2h
kube-apiserver-node1                    1/1     Running   1          7d2h
kube-controller-manager-node1           1/1     Running   2          7d2h
kube-flannel-ds-amd64-jtwgg             1/1     Running   1          7d1h
kube-flannel-ds-amd64-vl5hn             1/1     Running   1          7d2h
kube-proxy-22746                        1/1     Running   1          7d2h
kube-proxy-4tx62                        1/1     Running   1          7d1h
kube-scheduler-node1                    1/1     Running   3          7d2h
kubernetes-dashboard-5f7b999d65-59k42   1/1     Running   1          7d

配置Dashborad

為了能在瀏覽器中訪問dashboard，我們必須要先配置https證書。首先我們使用如下命令來生成私鑰和證書簽名

openssl genrsa -des3 -passout pass:x -out dashboard.pass.key 2048
openssl rsa -passin pass:x -in dashboard.pass.key -out dashboard.key
rm dashboard.pass.key
# 下面命令，一路回車
openssl req -new -key dashboard.key -out dashboard.csr

然后使用命令生成SSL證書

openssl x509 -req -sha256 -days 365 -in dashboard.csr -signkey dashboard.key -out dashboard.crt

在所有節(jié)點使用如下命令創(chuàng)建證書的掛載目錄

mkdir -p /var/share/certs

然后回到Master節(jié)點將生成的dashboard.key 和 dashboard.crt拷貝到/var/share/certs目錄下

創(chuàng)建admin-token.yaml文件，寫入如下內(nèi)容并保存

kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: adm
  annotations:
    rbac.authorization.kubernetes.io/autoupdateee: "true"
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io
subjects:
- kind: ServiceAccount
  name: admin
  namespace: kube-system
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: admin
  namespace: kube-system
  labels:
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: Reconcile

執(zhí)行kubectl create -f admin-token.yaml命令后，我們使用如下命令即可查看登入dashborad的token

kubectl get secret $(kubectl get secret -n kube-system|grep admin-token|awk '{print $1}') -n kube-system -o jsonpath={.data.token}|base64 -d |xargs echo

在瀏覽器輸入：https://IP:31234，然后選擇使用令牌登錄，將上一步命令輸出的token粘入即可登錄

參考

?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成，瀏覽時請結(jié)合常識與多方信息審慎甄別。
平臺聲明：文章內(nèi)容（如有圖片或視頻亦包括在內(nèi)）由作者上傳并發(fā)布，文章內(nèi)容僅代表作者本人觀點，簡書系信息發(fā)布平臺，僅提供信息存儲服務(wù)。

友情鏈接更多精彩內(nèi)容