Kubernetes-v1.17集群安装dashboard

最新推荐文章于 2024-05-27 16:38:25 发布
最新推荐文章于 2024-05-27 16:38:25 发布
阅读量6.4k 收藏 11
点赞数 7
分类专栏： Kubernetes 文章标签： kubernetes docker centos linux 大数据
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/zz_aiytag/article/details/103874977
版权

文章目录

环境说明

软件版本
centos7.4-1708
docker18.03.0-ce
kubernetes1.17.0

下载官方yaml文件

最新的配置文件v2.0.0-beta8版本recommended.yaml

官方UI文档

[root@master k8syaml]# wget https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/recommended.yaml
--2020-01-07 14:39:38--  https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/recommended.yaml
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.0.133, 151.101.64.133, 151.101.128.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.0.133|:443... failed: Connection timed out.
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.64.133|:443... failed: Connection timed out.
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.128.133|:443... failed: Connection timed out.
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.192.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7568 (7.4K) [text/plain]
Saving to: ‘recommended.yaml’

100%[====================================================================================================================================================================================================================================>] 7,568       3.02KB/s   in 2.4s   

2020-01-07 14:46:03 (3.02 KB/s) - ‘recommended.yaml’ saved [7568/7568]

编辑文件

修改接口

原文件内容

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

修改为

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

原文件内容

spec:
  containers:
    - name: kubernetes-dashboard
      image: kubernetesui/dashboard:v2.0.0-beta8
      imagePullPolicy: Always
      ports:
        - containerPort: 8443
          protocol: TCP

修改为

spec:
  # nodeName: master.node 指定到master节点，指不指定根据需要
  containers:
    - name: kubernetes-dashboard
      image: kubernetesui/dashboard:v2.0.0-beta8
      # imagePullPolicy: Always
      imagePullPolicy: IfNotPresent #不存在再下载
      ports:
        - containerPort: 8443
          protocol: TCP

下载镜像和启动

在master节点执行

[root@master k8syaml]# docker pull kubernetesui/dashboard:v2.0.0-beta8
v2.0.0-beta8: Pulling from kubernetesui/dashboard
5cd0d71945f0: Pull complete 
Digest: sha256:fc90baec4fb62b809051a3227e71266c0427240685139bbd5673282715924ea7
Status: Downloaded newer image for kubernetesui/dashboard:v2.0.0-beta8

[root@master k8syaml]# kubectl apply -f recommended.yaml
namespace/kubernetes-dashboard created
serviceaccount/kubernetes-dashboard created
service/kubernetes-dashboard created
secret/kubernetes-dashboard-certs created
secret/kubernetes-dashboard-csrf created
secret/kubernetes-dashboard-key-holder created
configmap/kubernetes-dashboard-settings created
role.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrole.rbac.authorization.k8s.io/kubernetes-dashboard created
rolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
deployment.apps/kubernetes-dashboard created
service/dashboard-metrics-scraper created
deployment.apps/dashboard-metrics-scraper created

查看pod和service状态

[root@master k8syaml]# kubectl get pods,svc -n kubernetes-dashboard -o wide
NAME                                             READY   STATUS    RESTARTS   AGE    IP           NODE           NOMINATED NODE   READINESS GATES
pod/dashboard-metrics-scraper-76585494d8-gbkzp   1/1     Running   0          2m9s   10.200.2.4   worker2.node   <none>           <none>
pod/kubernetes-dashboard-5f698b69fb-dxv8z        1/1     Running   0          2m9s   10.200.0.5   master.node    <none>           <none>

NAME                                TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)         AGE    SELECTOR
service/dashboard-metrics-scraper   ClusterIP   10.96.98.114   <none>        8000/TCP        2m9s   k8s-app=dashboard-metrics-scraper
service/kubernetes-dashboard        NodePort    10.96.97.104   <none>        443:30001/TCP   2m9s   k8s-app=kubernetes-dashboard

浏览器访问

浏览器上输入master节点https://IP:30001

火狐浏览器

firefox在接受风险并继续之后，可以打开界面
在这里插入图片描述

默认用户

选择用默认用户kubernetes-dashboard的token登陆
查看serviceaccount和secrets

[root@master k8syaml]# kubectl  get sa,secrets -n kubernetes-dashboard
NAME                                  SECRETS   AGE
serviceaccount/default                1         25m
serviceaccount/kubernetes-dashboard   1         25m

NAME                                      TYPE                                  DATA   AGE
secret/default-token-rf26t                kubernetes.io/service-account-token   3      25m
secret/kubernetes-dashboard-certs         Opaque                                0      25m
secret/kubernetes-dashboard-csrf          Opaque                                1      25m
secret/kubernetes-dashboard-key-holder    Opaque                                2      25m
secret/kubernetes-dashboard-token-ls8l4   kubernetes.io/service-account-token   3      25m

查看token

[root@master k8syaml]# kubectl describe secrets kubernetes-dashboard-token-ls8l4 -n kubernetes-dashboard
Name:         kubernetes-dashboard-token-ls8l4
Namespace:    kubernetes-dashboard
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: kubernetes-dashboard
              kubernetes.io/service-account.uid: ec58717f-ae47-4bfb-bff3-ffb677e73f2f

Type:  kubernetes.io/service-account-token

Data
====
ca.crt:     1025 bytes
namespace:  20 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6Ikh0ZVdaNkxaMkJtQ0Rpb3FZS1ZkRmxvTDhyWnNwRHV0VmtMLXk1ZlE2YzgifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZC10b2tlbi1sczhsNCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6ImVjNTg3MTdmLWFlNDctNGJmYi1iZmYzLWZmYjY3N2U3M2YyZiIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlcm5ldGVzLWRhc2hib2FyZDprdWJlcm5ldGVzLWRhc2hib2FyZCJ9.K-_hKDZfnjgHAK4b_a3Umm9deFtLJzI0pAown0vyNa8Gofx8pcyUkfT0IDMrkxnPLONbTUjom433WmR6e8TP0DlE0YKc_UgkhIY-viHEqdngrYujmJRC6thduITo5ysLoh6tI2h7XcgDoGfoWoUhJOl_SecoV45BpuEXF8xhxacXerHMSWKfaSCtI36gGkmz3yU6ds1MgabG2PTkU0yDEIgqm0YLoucM66Hp_4eL2M0mtbhDKsqERZhC67A2d13jRBwMmRCtk-8ogry1qf1iCXWcaZy2TV6Sj8Az3_0NDm6IqdEEHEMp0_eEDJDgCf9a6ZG0Dm4PK8vtoFX7LrW5GQ

或者

[root@master k8syaml]# kubectl describe secrets  $(kubectl  get secrets -n kubernetes-dashboard | awk  '/kubernetes-dashboard-token/{print $1}' ) -n kubernetes-dashboard |sed -n '/token:.*/p'
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6Ikh0ZVdaNkxaMkJtQ0Rpb3FZS1ZkRmxvTDhyWnNwRHV0VmtMLXk1ZlE2YzgifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZC10b2tlbi1sczhsNCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6ImVjNTg3MTdmLWFlNDctNGJmYi1iZmYzLWZmYjY3N2U3M2YyZiIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlcm5ldGVzLWRhc2hib2FyZDprdWJlcm5ldGVzLWRhc2hib2FyZCJ9.K-_hKDZfnjgHAK4b_a3Umm9deFtLJzI0pAown0vyNa8Gofx8pcyUkfT0IDMrkxnPLONbTUjom433WmR6e8TP0DlE0YKc_UgkhIY-viHEqdngrYujmJRC6thduITo5ysLoh6tI2h7XcgDoGfoWoUhJOl_SecoV45BpuEXF8xhxacXerHMSWKfaSCtI36gGkmz3yU6ds1MgabG2PTkU0yDEIgqm0YLoucM66Hp_4eL2M0mtbhDKsqERZhC67A2d13jRBwMmRCtk-8ogry1qf1iCXWcaZy2TV6Sj8Az3_0NDm6IqdEEHEMp0_eEDJDgCf9a6ZG0Dm4PK8vtoFX7LrW5GQ

用上面得到的token登陆之后，界面上数据显示不出来
并提示权限不足
在这里插入图片描述

新增管理员用户

新建一个create-admin.yaml
填入以下内容

apiVersion: v1
kind: ServiceAccount
metadata:
  name: admin-user
  namespace: kubernetes-dashboard

---

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

保存退出，并执行

[root@master k8syaml]# kubectl apply -f create-admin.yaml 
serviceaccount/admin-user created
clusterrolebinding.rbac.authorization.k8s.io/admin-user created

查看sa和secret

[root@master k8syaml]# kubectl get sa,secrets -n kubernetes-dashboard
NAME                                  SECRETS   AGE
serviceaccount/admin-user             1         64s
serviceaccount/default                1         42m
serviceaccount/kubernetes-dashboard   1         42m

NAME                                      TYPE                                  DATA   AGE
secret/admin-user-token-t79xh             kubernetes.io/service-account-token   3      64s
secret/default-token-rf26t                kubernetes.io/service-account-token   3      42m
secret/kubernetes-dashboard-certs         Opaque                                0      42m
secret/kubernetes-dashboard-csrf          Opaque                                1      42m
secret/kubernetes-dashboard-key-holder    Opaque                                2      42m
secret/kubernetes-dashboard-token-ls8l4   kubernetes.io/service-account-token   3      42m

[root@master k8syaml]# kubectl describe secret admin-user-token-t79xh -n kubernetes-dashboard
Name:         admin-user-token-t79xh
Namespace:    kubernetes-dashboard
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: admin-user
              kubernetes.io/service-account.uid: 0723ea98-f2e7-47ce-a954-eb99013dda47

Type:  kubernetes.io/service-account-token

Data
====
ca.crt:     1025 bytes
namespace:  20 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6Ikh0ZVdaNkxaMkJtQ0Rpb3FZS1ZkRmxvTDhyWnNwRHV0VmtMLXk1ZlE2YzgifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJhZG1pbi11c2VyLXRva2VuLXQ3OXhoIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6ImFkbWluLXVzZXIiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiIwNzIzZWE5OC1mMmU3LTQ3Y2UtYTk1NC1lYjk5MDEzZGRhNDciLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3ViZXJuZXRlcy1kYXNoYm9hcmQ6YWRtaW4tdXNlciJ9.aaQgyqDJ217d4sxv0uPL6lSVntQmq3NLM2g5w3newhj4rBkXW1RGmKJQtuqSEx4CeGlbPknl1nsFrG4Z0WOSa2ZHj8zDI1YXaxNmpuOPYC94TMYpfK1p1tSVXYJhrnPggQmsa-O7m3S7cNkPgFtpS_GMgGqdh6zWTzQVQyvMHrWcczCe3kW4XJzU7F-v8uEzD5m7Kn7iivV9L4PMqtOb7_qeeDzuMLmAnmJREDyiE7lumc_ZfdoDdHS6jbmv_J4yFf0YWu_lqXbM1mLFdfTVjVcsIuGqGwXM2YZ7nnuIrZwNTiXoJcL4rK8sBvbgfrgIt-iqA3VlcbYYqLiNeTxLNQ

或者用下面这种方法

# 创建serviceaccount
[root@master k8syaml]# kubectl create serviceaccount admin-myuser -n kubernetes-dashboard
serviceaccount/admin-myuser created
# sa绑定集群管理员
[root@master k8syaml]# kubectl create clusterrolebinding  dashboard-cluster-admin --clusterrole=cluster-admin --serviceaccount=kubernetes-dashboard:admin-myuser
clusterrolebinding.rbac.authorization.k8s.io/dashboard-cluster-admin created
[root@master k8syaml]# kubectl get sa,secrets -n kubernetes-dashboard
NAME                                  SECRETS   AGE
serviceaccount/admin-myuser           1         84s
serviceaccount/default                1         58m
serviceaccount/kubernetes-dashboard   1         58m

NAME                                      TYPE                                  DATA   AGE
secret/admin-myuser-token-275f9           kubernetes.io/service-account-token   3      87s
secret/default-token-rf26t                kubernetes.io/service-account-token   3      58m
secret/kubernetes-dashboard-certs         Opaque                                0      58m
secret/kubernetes-dashboard-csrf          Opaque                                1      58m
secret/kubernetes-dashboard-key-holder    Opaque                                2      58m
secret/kubernetes-dashboard-token-ls8l4   kubernetes.io/service-account-token   3      58m

查看token

[root@master k8syaml]# kubectl describe secret admin-myuser-token-275f9 -n kubernetes-dashboard
Name:         admin-myuser-token-275f9
Namespace:    kubernetes-dashboard
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: admin-myuser
              kubernetes.io/service-account.uid: bfcb1bdc-4740-4c3a-9e36-2602842b96a7

Type:  kubernetes.io/service-account-token

Data
====
ca.crt:     1025 bytes
namespace:  20 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6Ikh0ZVdaNkxaMkJtQ0Rpb3FZS1ZkRmxvTDhyWnNwRHV0VmtMLXk1ZlE2YzgifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJhZG1pbi1teXVzZXItdG9rZW4tMjc1ZjkiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC5uYW1lIjoiYWRtaW4tbXl1c2VyIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQudWlkIjoiYmZjYjFiZGMtNDc0MC00YzNhLTllMzYtMjYwMjg0MmI5NmE3Iiwic3ViIjoic3lzdGVtOnNlcnZpY2VhY2NvdW50Omt1YmVybmV0ZXMtZGFzaGJvYXJkOmFkbWluLW15dXNlciJ9.ysqLRFHBXOPOZjLDbn8Vd02hvhPnS7Tt4XhQRscXBTY7D8b57R2Lz7AR-uF6k7hP5cU15we7bVXMVjGelezFpblLMxiB0EM0w6HN82yucPZRGFW4S8SPN2Mz6CoIYBHT72wwSvgKXtNqnhezG1RaQ-R4dPrZBVKVNBNIqBaHbmD8wOq-GJQ49FOdLMQZ1Rj_UCALoJlxLPC5xlQGrtQQHzgbx4bbwqaswG_wN-uIUp8Q-5re1be1E9qpior4f6gwGYJLG2-kfcum3aBEC7AK9tqLhcOuEEnFY73HMUfS2ha-vrEXEDIs5T72YQ7JFr2njJMvBw9fK-HZfi2CyWkQrQ

使用上述两种方法任一均可，拿到token后重新登陆，可正常显示数据了
在这里插入图片描述

谷歌浏览器

仅做上述修改无法打开，显示以下信息

10.XX.XX.52 通常会使用加密技术来保护您的信息。Google Chrome 此次尝试连接到 10.XX.XX.52 时，此网站发回了异常的错误凭据。这可能是因为有攻击者在试图冒充 10.XX.XX.52，或 Wi-Fi
登录屏幕中断了此次连接。请放心，您的信息仍然是安全的，因为 Google Chrome 尚未进行任何数据交换便停止了连接。

您目前无法访问 10.XX.XX.52，因为此网站发送了 Google Chrome
无法处理的杂乱凭据。网络错误和攻击通常是暂时的，因此，此网页稍后可能会恢复正常。

先把之前启动的资源全部删除掉

[root@master k8syaml]# kubectl delete -f recommended.yaml 
namespace "kubernetes-dashboard" deleted
serviceaccount "kubernetes-dashboard" deleted
service "kubernetes-dashboard" deleted
secret "kubernetes-dashboard-certs" deleted
secret "kubernetes-dashboard-csrf" deleted
secret "kubernetes-dashboard-key-holder" deleted
configmap "kubernetes-dashboard-settings" deleted
role.rbac.authorization.k8s.io "kubernetes-dashboard" deleted
clusterrole.rbac.authorization.k8s.io "kubernetes-dashboard" deleted
rolebinding.rbac.authorization.k8s.io "kubernetes-dashboard" deleted
clusterrolebinding.rbac.authorization.k8s.io "kubernetes-dashboard" deleted
deployment.apps "kubernetes-dashboard" deleted
service "dashboard-metrics-scraper" deleted
deployment.apps "dashboard-metrics-scraper" deleted

需要额外修改recommended.yaml
以下内容全部注释掉

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

自己生成kubernetes-dashboard-certs
新建一个目录并进入

# 生成 key
[root@master create_cert]# openssl genrsa -out dashboard.key 2048
Generating RSA private key, 2048 bit long modulus
............................+++
.+++
e is 65537 (0x10001)
[root@master create_cert]# ll
total 4
-rw-r--r-- 1 root root 1675 Jan  7 17:31 dashboard.key
[root@master create_cert]# openssl req -days 36000   -new -out dashboard.csr    -key dashboard.key   -subj '/CN=**10.180.249.52**'
[root@master create_cert]# ll
total 8
-rw-r--r-- 1 root root  903 Jan  7 17:32 dashboard.csr
-rw-r--r-- 1 root root 1675 Jan  7 17:31 dashboard.key
# 生成自签证书
[root@master create_cert]# openssl x509 -req -in dashboard.csr -signkey dashboard.key -out dashboard.crt
Signature ok
subject=/CN=**10.180.249.52**
Getting Private key
[root@master create_cert]# ll
total 12
-rw-r--r-- 1 root root  997 Jan  7 17:32 dashboard.crt
-rw-r--r-- 1 root root  903 Jan  7 17:32 dashboard.csr
-rw-r--r-- 1 root root 1675 Jan  7 17:31 dashboard.key
# 使用自签证书创建secret
[root@master create_cert]# kubectl create secret generic kubernetes-dashboard-certs     --from-file=dashboard.key     --from-file=dashboard.crt      -n kubernetes-dashboard
secret/kubernetes-dashboard-certs created

再次启动应用

[root@master k8syaml]# kubectl apply -f recommended.yaml 
namespace/kubernetes-dashboard created
serviceaccount/kubernetes-dashboard created
service/kubernetes-dashboard created
secret/kubernetes-dashboard-csrf created
secret/kubernetes-dashboard-key-holder created
configmap/kubernetes-dashboard-settings created
role.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrole.rbac.authorization.k8s.io/kubernetes-dashboard created
rolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
deployment.apps/kubernetes-dashboard created
service/dashboard-metrics-scraper created
deployment.apps/dashboard-metrics-scraper created

稍等片刻查看pod和service信息

[root@master create_cert]# kubectl get pods,svc -n kubernetes-dashboard -o wide
NAME                                             READY   STATUS    RESTARTS   AGE     IP           NODE           NOMINATED NODE   READINESS GATES
pod/dashboard-metrics-scraper-76585494d8-mq62z   1/1     Running   0          6m15s   10.200.1.4   worker1.node   <none>           <none>
pod/kubernetes-dashboard-5f698b69fb-44vxj        1/1     Running   0          6m15s   10.200.0.6   master.node    <none>           <none>

NAME                                TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE     SELECTOR
service/dashboard-metrics-scraper   ClusterIP   10.96.183.245   <none>        8000/TCP        6m15s   k8s-app=dashboard-metrics-scraper
service/kubernetes-dashboard        NodePort    10.96.106.179   <none>        443:30001/TCP   6m15s   k8s-app=kubernetes-dashboard

查看sa和secret信息

[root@master k8syaml]# kubectl get sa,secrets -n kubernetes-dashboard
NAME                                  SECRETS   AGE
serviceaccount/default                1         19m
serviceaccount/kubernetes-dashboard   1         19m

NAME                                      TYPE                                  DATA   AGE
secret/default-token-kjrs9                kubernetes.io/service-account-token   3      19m
secret/kubernetes-dashboard-certs         Opaque                                2      14m
secret/kubernetes-dashboard-csrf          Opaque                                1      19m
secret/kubernetes-dashboard-key-holder    Opaque                                2      19m
secret/kubernetes-dashboard-token-bhcxb   kubernetes.io/service-account-token   3      19m

在浏览器上打开https://IP:30001,可以正常打开，选择高级-继续前往即可打开登陆页面
在这里插入图片描述
正常使用仍然需要新建管理员用户，参考火狐部分。

参考

再看我把你吃掉
关注
  • 7
    点赞
  • 踩
  • 11
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
k8s1.17与dashboard与metricserver部署.docx
03-17
kube1.17，dashboard，metres-server部署文档整理，centos7.x以上已经完成部署，亲测好用。
kubernetes-dashboard-amd64-v1.8.3镜像包
05-13
kubernetes-dashboard-amd64-v1.8.3镜像包，由于国外镜像无法下载，可以用这个包load到本地镜像，再上传到你的私有仓库，实现离线部署安装dashboard。解压后有操作命令
K8s1.17部署Dashboard2.0（上）
IT教育任姐姐的博客
11-24 2643
自己制作证书 1、删除上面创建的各种资源 #kubectldelete-fcreate-admin.yaml #kubectldelete-fdashboard-admin-bind-clusterrole.yaml #kubectldelete-frecommended.yaml 2、修改recommended.yaml⽂件 #因为我们要⼿动创建名称空间，把这⾥的创建删除掉，不然如果出了 错⽤yaml删除ns的时候也会把⾥⾯的资源全部删掉 #apiVersion:...
Kubernetes可视化界面之DashBoard
最新发布
weixin_72583321的博客
05-27 1139
Kubernetes Dashboard 是 Kubernetes 社区提供的一个基于网页的用户界面，它允许用户通过图形界面管理 Kubernetes 集群中的资源。Dashboard 提供了一种直观易用的方式来部署和管理容器应用，同时也能对应用进行故障排除和集群资源管理。通过 Dashboard，用户可以获取集群中应用的概览信息，创建或修改 Kubernetes 资源（如 Deployment、Job、DaemonSet 等），并对 Deployment 进行弹性伸缩、滚动升级、重启 Pod 等操作。此外
k8s dashboard_【大强哥-k8s从入门到放弃02】Kubernetes1.17部署Dashboard2.0
weixin_39562615的博客
11-16 220
号外号外，后面所有提升视频都会更新到知乎和B站上去，不会直接发群里了，哈哈，能看懂这句话的我都认识，大家可以先关注一下，我知乎上的所有文档也会录成视频更多视频详见 杨哥天云：https://space.bilibili.com/514805677我马上就开B站账号，录制点儿走心的视频，呼呼开始正题注：因为本次部署在Centos8.1上，Dashboard必须使用2.0-rc6以上版本，rc6以下测...
K8s1.17部署Dashboard2.0（下）
IT教育任姐姐的博客
11-24 3398
注：因为本次部署在Centos8.1上，Dashboard必须使⽤2.0-rc6以 上版本，rc6以下测试部署不成功 Dashboard介绍 Dashboard 是基于⻚的 Kubernetes ⽤户界⾯。您可以使⽤ Dashboard 将容器应⽤部署到 Kubernetes 集群中，也可以对容器应 ⽤排错，还能管理集群资源。您可以使⽤ Dashboard 获取运⾏在集群 中的应⽤的概览信息，也可以创建或者修改 Kubernetes 资源（如 Deployment，Job，DaemonSet 等..
k8s-安装dashboard
栋院
03-02 543
1、 执行yaml文件安装dashboard kubectl create -f kubernetes-dashboard.yaml 2、查看dashboard pod及svc状态 3、配置dashboard外网访问 kubectl get svc,pod -n kubernetes-dashboard type: NodePort 4、浏览器访问 https://192.168.241.191:30801/ 5 、创建用户授予管理员权限 kubectl create .
kubernetes-dashboard-amd64-v1.10.0镜像
12-03
kubernetes-dashboard-amd64-v1.10.0镜像，docker load -i kubernetes-dashboard-amd64-v1.10.0.tgz
kubernetes-dashboard-v1.8.3 yaml文件
10-08
在使用 `kubernetes-dashboard-v1.8.3.yaml` 文件时，首先需要确保你的 Kubernetes 集群已经安装并运行正常，且你有相应的权限来操作集群。然后，执行以下步骤： 1. **下载 YAML 文件**：获取 `kubernetes-...
kubernetes-dashboard.yaml
08-11
image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1 imagePullPolicy: IfNotPresent ports: - containerPort: 8443 protocol: TCP args: - --auto-generate-certificates # Uncomment the following ...
kubernetes-dashboard-amd64-v1.8.3
09-27
kubernetes-dashboard-amd64-v1.8.3镜像，镜像使用方法： docker load -i kubernetes-dashboard-amd64-v1.8.3.tar.gz
k8s dashboard 部署总结
03-31
k8s dashboard 部署总结 k8s dashboard 部署总结 k8s dashboard 部署总结
k8s入门：kubernetes-dashboard 安装
不懂一休
07-01 1万+
第一章：✨ k8s入门：裸机部署 k8s 集群 第二章：✨ k8s入门：部署应用到 k8s 集群 第三章：✨ k8s入门：service 简单使用 第四章：✨ k8s入门：StatefulSet 简单使用 第五章：✨ k8s入门：存储（storage） 第六章：✨ K8S 配置 storageclass 使用 nfs 动态申领本地磁盘空间 第七章：✨ k8s入门：配置 ConfigMap & Secret 第八章：✨ [k8s入门：k8s入门：Helm 构建 MySQL]https://yixiu.blog
Kubernetes Dashboard部署安装
lpfstudy的博客
07-17 7196
创建dashboard成功！跟grafana差不多。
Cisco配置：主机名、标语、线路和密码。使用 cisco 作为用户 EXEC 密码，class 作为特权 EXEC 密码。cisco作为vty密码 ，加密所有密码，配置ip（4/6）地址
热门推荐
Joker.Dragon
05-25 4万+
主机名 标语 使用 cisco 作为用户 EXEC 密码， class 作为特权 EXEC 密码。 cisco作为vty密码 ， 加密所有密码。 enable configure terminal hostname Branch-A banner motd #Branch-A# enable password class line console 0 password cisco logi...
拆除二进制炸弹
capsnever的博客
11-24 4716
Writed by 20.4 隋春雨 文章目录1. 第一关2. 第二关3. 第三关4. 第四关5. 第五关6. 第六关 参考文章： 常见指令 MIPS指令官方文档 gdb调试 stack如何保存现场？ 常见寄存器： 1. 第一关 从beqz指令那里可以看出，如果是字符串相等的话，那么我们就直接跳到 0x400da4，可以看到0x00400d9c是炸弹爆炸的地方，所以这一关的要点就变成了，查出原来的函数中保存的string的内容，然后输入即可 本来我最开始看到这个\就不太理解，后来用pycharm输出
kubernetes1.16.3、1.17.4高可用集群安装
03-18
本套课程会带领大家学习kubernetes1.16.3，kubernetes1.17.4高可用集群的安装，通过keepalive+lvs实现master节点apiserver的高可用，同时会安装dashboard和metrics等附加组件
kubernetes dashboard访问不了
weixin_44968234的博客
03-21 1028
背景：更新了chrome之后，之前一直可以访问的kubernetes dashboard突然访问失败，一开始以为是pod有问题，删除更新后依旧访问不了；找到chrome图标右键、属性，添加以下信息就可以正常访问了。“您的连接不是私密链接”
部署k8s-dashboard完成以后访问出现错误v
iouczp的博客
05-13 6701
原文：http://dockone.io/question/1266浏览器访问8080端跳转出现这个，是什么原因Error: 'dial tcp 172.17.34.2:9090: getsockopt: connection refused'Trying to reach: 'http://172.17.34.2:9090/'求各位大神支招 qq 2323273838pod文件是官方的Copyr...
kubectl -n kubernetes-dashboard create token kubernetes-dashboard
05-23
这个命令会在 kubernetes-dashboard 命名空间中创建一个新的 token，用于访问 Kubernetes Dashboard。但是，这个命令是不完整的，需要提供 token 的具体信息。完整的命令应该是： ``` kubectl -n kubernetes-dashboard create serviceaccount dashboard-admin kubectl -n kubernetes-dashboard create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kubernetes-dashboard:dashboard-admin kubectl -n kubernetes-dashboard describe secret $(kubectl -n kubernetes-dashboard get secret | grep dashboard-admin | awk '{print $1}') ``` 这个命令会创建一个名为 dashboard-admin 的 ServiceAccount，并将其与 cluster-admin 角色进行绑定。然后，它将输出一个 secret 的名称，你可以使用该 secret 中的 token 来访问 Kubernetes Dashboard。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值