1、Kubernetes Dashboard 是 k8s集群的⼀个 WEB UI管理⼯具，代码托管在 github 上，地址：
https://github.com/kubernetes/dashboard

　2、安装直接使用官方文件就行(如果地址失效去github 看一下)

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

kubectl apply -f  kubernetes-dashboard.yaml

　3、我在master执行完现在如下

[root@master ~]# kubectl get pods --all-namespaces

NAMESPACE     NAME                                    READY   STATUS    RESTARTS   AGE

kube-system   coredns-576cbf47c7-2g27x                1/1     Running   0          18h

kube-system   coredns-576cbf47c7-47mgd                1/1     Running   0          18h

kube-system   etcd-master                             1/1     Running   0          18h

kube-system   kube-apiserver-master                   1/1     Running   0          18h

kube-system   kube-controller-manager-master          1/1     Running   0          18h

kube-system   kube-flannel-ds-amd64-hw277             1/1     Running   4          18h

kube-system   kube-flannel-ds-amd64-j5jcr             1/1     Running   1          18h

kube-system   kube-proxy-8tfsp                        1/1     Running   1          18h

kube-system   kube-proxy-k6k79                        1/1     Running   0          18h

kube-system   kube-scheduler-master                   1/1     Running   0          18h

kube-system   kubernetes-dashboard-65c76f6c97-htfxt   1/1     ImagePullBackOff 0 18h

 #ImagePullBackOff：这个状态是有问题的，然后我就各种百度，从启服务器，发下没有什么卵用啊，初学就是比较费劲，然后才百度出来下面的解决方法
[root@master ~]# kubectl describe -n kube-system pod/kubernetes-dashboard-65c76f6c97-htfxt

Name:               kubernetes-dashboard-65c76f6c97-htfxt

Namespace:          kube-system

Priority:           0

PriorityClassName:  <none>

Node:               node01/172.21.0.14

Start Time:         Sun, 13 Oct 2019 19:42:52 +0800

Labels:             k8s-app=kubernetes-dashboard

                    pod-template-hash=65c76f6c97

Annotations:        <none>

Status:             Running

IP:                 10.244.1.3

Controlled By:      ReplicaSet/kubernetes-dashboard-65c76f6c97

Containers:

  kubernetes-dashboard:

    Container ID:  docker://7f9d2b3f22112c761af8c451376fb2155ac2014f7c13a4a7cda8ebcefebb0de3

    Image:         k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1

    Image ID:      docker://sha256:f9aed6605b814b69e92dece6a50ed1e4e730144eb1cc971389dde9cb3820d124

    Port:          8443/TCP

    Host Port:     0/TCP

    Args:

      --auto-generate-certificates

    State:          Running

      Started:      Sun, 13 Oct 2019 20:20:58 +0800

    Ready:          True

    Restart Count:  0

    Liveness:       http-get https://:8443/ delay=30s timeout=30s period=10s #success=1 #failure=3

    Environment:    <none>

    Mounts:

      /certs from kubernetes-dashboard-certs (rw)

      /tmp from tmp-volume (rw)

      /var/run/secrets/kubernetes.io/serviceaccount from kubernetes-dashboard-token-m4s7k (ro)

Conditions:

  Type              Status

  Initialized       True

  Ready             True

  ContainersReady   True

  PodScheduled      True

Volumes:

  kubernetes-dashboard-certs:

    Type:        Secret (a volume populated by a Secret)

    SecretName:  kubernetes-dashboard-certs

    Optional:    false

  tmp-volume:

    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)

    Medium:

  kubernetes-dashboard-token-m4s7k:

    Type:        Secret (a volume populated by a Secret)

    SecretName:  kubernetes-dashboard-token-m4s7k

    Optional:    false

QoS Class:       BestEffort

Node-Selectors:  <none>

Tolerations:     node-role.kubernetes.io/master:NoSchedule

                 node.kubernetes.io/not-ready:NoExecute for 300s

                 node.kubernetes.io/unreachable:NoExecute for 300s

Events:

  Type     Reason                  Age                 From               Message

  ----     ------                  ----                ----               -------

  Normal   Scheduled               60m                 default-scheduler  Successfully assigned kube-system/kubernetes-dashboard-65c76f6c97-htfxt to node01

  Normal   Pulling                 58m (x4 over 60m)   kubelet, node01    pulling image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1"

  Warning  Failed                  58m (x4 over 60m)   kubelet, node01    Failed to pull image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1": rpc error: code = Unknown desc = Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

  Warning  Failed                  58m (x4 over 60m)   kubelet, node01    Error: ErrImagePull

  Normal   BackOff                 57m (x6 over 60m)   kubelet, node01    Back-off pulling image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1"

  Warning  Failed                  50m (x37 over 60m)  kubelet, node01    Error: ImagePullBackOff

  Warning  FailedMount             28m                 kubelet, node01    MountVolume.SetUp failed for volume "kubernetes-dashboard-certs" : couldn't propagate object cache: timed out waiting for the condition

  Warning  FailedMount             28m                 kubelet, node01    MountVolume.SetUp failed for volume "kubernetes-dashboard-token-m4s7k" : couldn't propagate object cache: timed out waiting for the condition

  Warning  FailedCreatePodSandBox  28m                 kubelet, node01    Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "0ac235fed359b9d102282bcc816ff3de7c9e26d18270067761f5304aa998d747" network for pod "kubernetes-dashboard-65c76f6c97-htfxt": NetworkPlugin cni failed to set up pod "kubernetes-dashboard-65c76f6c97-htfxt_kube-system" network: open /run/flannel/subnet.env: no such file or directory

  Warning  FailedCreatePodSandBox  28m                 kubelet, node01    Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "233c431e6bceddf5f315f1b8aac762359202ca5a13cd4e4d2fd6a2aaf4123cd2" network for pod "kubernetes-dashboard-65c76f6c97-htfxt": NetworkPlugin cni failed to set up pod "kubernetes-dashboard-65c76f6c97-htfxt_kube-system" network: open /run/flannel/subnet.env: no such file or directory

  Normal   SandboxChanged          28m (x3 over 28m)   kubelet, node01    Pod sandbox changed, it will be killed and re-created.

  Warning  FailedCreatePodSandBox  28m                 kubelet, node01    Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "0de536b8aa18baa69b6fbdd645063b61ee7fe0fb141b063a0387872e216a6d18" network for pod "kubernetes-dashboard-65c76f6c97-htfxt": NetworkPlugin cni failed to set up pod "kubernetes-dashboard-65c76f6c97-htfxt_kube-system" network: open /run/flannel/subnet.env: no such file or directory

  Normal   Pulling                 27m (x3 over 28m)   kubelet, node01    pulling image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1"

  Warning  Failed                  27m (x3 over 28m)   kubelet, node01    Failed to pull image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1": rpc error: code = Unknown desc = Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

  Warning  Failed                  27m (x3 over 28m)   kubelet, node01    Error: ErrImagePull

  Normal   BackOff                 26m (x4 over 28m)   kubelet, node01    Back-off pulling image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1"

  Warning  Failed                  23m (x14 over 28m)  kubelet, node01    Error: ImagePullBackOff

结果是镜像不存在，我是阿里云所有直接从阿里云pull,在打包，然后在看，还是不行，然后又一顿百度，

docker pull  mirrorgooglecontainers/kubernetes-dashboard-amd64:v1.10.1

docker tag mirrorgooglecontainers/kubernetes-dashboard-amd64:v1.10.1 k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1

　一顿百度解决方法如下： 查看详细信息，发下pod在node01 上运行的，然后吧镜像save 一份到node01服务器就好了，或者直接在node01上面直接pull

[root@master ~]# kubectl  get pods --all-namespaces -o wide

NAMESPACE     NAME                                    READY   STATUS    RESTARTS   AGE   IP            NODE     NOMINATED NODE

kube-system   coredns-576cbf47c7-2g27x                1/1     Running   0          18h   10.244.0.4    master   <none>

kube-system   coredns-576cbf47c7-47mgd                1/1     Running   0          18h   10.244.0.5    master   <none>

kube-system   etcd-master                             1/1     Running   0          18h   172.21.0.10   master   <none>

kube-system   kube-apiserver-master                   1/1     Running   0          18h   172.21.0.10   master   <none>

kube-system   kube-controller-manager-master          1/1     Running   0          18h   172.21.0.10   master   <none>

kube-system   kube-flannel-ds-amd64-hw277             1/1     Running   4          18h   172.21.0.14   node01   <none>

kube-system   kube-flannel-ds-amd64-j5jcr             1/1     Running   1          18h   172.21.0.10   master   <none>

kube-system   kube-proxy-8tfsp                        1/1     Running   1          18h   172.21.0.14   node01   <none>

kube-system   kube-proxy-k6k79                        1/1     Running   0          18h   172.21.0.10   master   <none>

kube-system   kube-scheduler-master                   1/1     Running   0          18h   172.21.0.10   master   <none>

kube-system   kubernetes-dashboard-65c76f6c97-htfxt   1/1     Running   0          18h   10.244.1.3    node01   <none>

　4、删除现有的dashboard服务，dashboard服务的namespace是kube-system，但是该服务的类型是ClusterIP，不便于我们通过浏览器访问，因此需要改成NodePort型的；

kubectl delete service kubernetes-dashboard --namespace=kube-system

　5、执行以下命令，创建dashboard服务的配置文件

cat <<EOF >  ~/dashboard-svc.yaml

kind: Service

apiVersion: v1

metadata:

  labels:

    k8s-app: kubernetes-dashboard

  name: kubernetes-dashboard

  namespace: kube-system

spec:

  type: NodePort

  ports:

    - port: 443

      targetPort: 8443

  selector:

    k8s-app: kubernetes-dashboard

EOF

　6、用刚刚创建的yaml文件创建新的dashboard服务：　

kubectl create -f ~/dashboard-svc.yaml

　7、想要访问dashboard服务，就要有访问权限，这里需要先设置一个dashboard服务的权限和绑定关系，执行以下命令创建对应的资源文件dashboard-svc-account.yaml：　

cat <<EOF >  ~/dashboard-svc-account.yaml

apiVersion: v1

kind: ServiceAccount

metadata:

  labels:

    k8s-app: kubernetes-dashboard

  name: kubernetes-dashboard-admin

  namespace: kube-system

---

apiVersion: rbac.authorization.k8s.io/v1beta1

kind: ClusterRoleBinding

metadata:

  name: kubernetes-dashboard-admin

  labels:

    k8s-app: kubernetes-dashboard

roleRef:

  apiGroup: rbac.authorization.k8s.io

  kind: ClusterRole

  name: cluster-admin

subjects:

- kind: ServiceAccount

  name: kubernetes-dashboard-admin

  namespace: kube-system

EOF

8、执行命令创建ServiceAccount和ClusterRoleBinding：

kubectl create -f ~/dashboard-svc-account.yaml

9、找出secret，这个secret中有token，该token是登录dashboard时用到的

[root@master data]# kubectl -n kube-system get secret|egrep  kubernetes-dashboard-admin

kubernetes-dashboard-admin-token-2q42n           kubernetes.io/service-account-token   3      18h

10、查看kubernetes-dashboard-admin-token-2q42n 的详情，里面有对应的token信息：　　

kubectl describe -n kube-system secret/kubernetes-dashboard-admin-token-2q42n|egrep token:

11、查看pod 位于node01节点：

kubectl describe -n kube-system pod/kubernetes-dashboard-65c76f6c97-htfxt

#查看服务

kubectl get svc -n kube-system

12、用Firefox访问   https://ip:31330     地址，得到以下提示：

13、创建以config方式登录dashborad的用户参考

https://blog.51cto.com/dellinger/2442038　

k8s安装dashboard的更多相关文章

  1. 【K8S】K8S 1.18.2安装dashboard（基于kubernetes-dashboard 2.0.0版本）

    [K8S]K8S 1.18.2安装dashboard(基于kubernetes-dashboard 2.0.0版本) 写在前面 K8S集群部署成功了,如何对集群进行可视化管理呢?别着急,接下来,我们一 ...

  2. k8s 安装步骤

    1 安装Docker 1.1 增加中国区镜像 https://registry.docker-cn.com 2 下载安装k8s的镜像的脚本 https://github.com/AliyunConta ...

  3. k8s安装部署过程个人总结及参考文章

    以下是本人安装k8s过程 一.单机配置 1. 环境准备 主机名 IP 配置 master1 192.168.1.181 1C 4G 关闭所有节点的seliux以及firewalld sed -i 's ...

  4. kubernetes（安装dashboard）

    https://blog.csdn.net/qq_22917163/article/details/84527420 1. 通过yaml文件安装dashboard 我们可以从https://githu ...

  5. Kubernetes 入门-学习-nginx安装-dashboard安装

    一.入门 1.Kubernetes中文社区---http://docs.kubernetes.org.cn/ 2.Kubernetes集群组件: - etcd 一个高可用的K/V键值对存储和服务发现系 ...

  6. Kubernetes(K8s) 安装（使用kubeadm安装Kubernetes集群）

    背景: 由于工作发生了一些变动,很长时间没有写博客了. 概述: 这篇文章是为了介绍使用kubeadm安装Kubernetes集群(可以用于生产级别).使用了Centos 7系统. 一.Centos7 ...

  7. kubernetes系列(十七) - 通过helm安装dashboard详细教程

    1. 前提条件 2. 配置https证书为secret 3. dashboard安装 3.1 helm拉取dashboard的chart 3.2 配置dashboard的chart包配置 3.3 he ...

  8. kubeadm部署安装+dashboard+harbor

    kubeadm 部署安装+dashboard+harbor master(2C/4G,cpu核心数要求大于2) 192.168.80.10 docker.kubeadm.kubelet.kubectl ...

  9. K8S 部署Dashboard UI

    Kubernetes Dashboard是Kubernetes集群的通用.基于Web的UI.它允许用户管理集群中运行的应用程序并对其进行故障排除,以及管理集群本身. 访问到DashBoard有两种方式 ...

随机推荐

  1. C# vb .NET识别读取QR二维码

    二维码比条形码具有更多优势,有些场合使用二维码比较多,比如支付.那么如何在C#,.Net平台代码里读取二维码呢?答案是使用SharpBarcode! SharpBarcode是C#快速高效.准确的条形 ...

  2. 2-kong的preserve_host和strip_uri解析

    原文参考:https://www.cnblogs.com/mentalidade/p/6847004.html preserve_host:当代理的时候,k代理时,Kong的默认行为是将上游请求的Ho ...

  3. English--比较结构

    English|比较结构 接下来让我们一起来透析,英语中的比较结构.各位同学,带上小板凳,要认真哦~ 前言 目前所有的文章思想格式都是:知识+情感. 知识:对于所有的知识点的描述.力求不含任何的自我感 ...

  4. nginx配置多个TLS证书，以及TLS SNI简介

    背景 原来申请的正式域名备案通过,TLS证书也申请了.之前使用的临时域名和证书作为测试环境使用.于是要在单个ECS主机上配置nginx多个证书和多个域名. 实践 nginx部署多个TLS证书很简单,在 ...

  5. 左右对齐Justify遇到的坑

    遇到的问题 这两天在开发一个病历的对外展示页面,设计稿上label是左右拉伸对齐的,显示效果如下: 怎么实现这种效果呢? 首先想到的是文字中间加空格,但是这种方式太low了,而且不太容易控制.网上查资 ...

  6. preflight request预检请求

    preflight request预检请求,负责检查是否允许跨域请求,但是注意并不是所有的跨域请求都会发送preflight请求.对与那些幂等的请求,如GET请求,就不会发送preflight请求.只 ...

  7. python列表推导式及其简单应用

    列表推导式(又称列表解析式)提供了一种简明扼要的方法来创建列表 一个简单平方 普通for循环 for i in range(1,5): print(i*i,end='') 列表推导式 res = [x ...

  8. VMware vSphere API开发（一）---vSphere 体系核心概念

    1.VMware SDDC        VMware 软件定义数据中心(software defined dataCenter,SDDC),包括了从最底层的VMware vSphere.软件定义存储 ...

  9. Golang 需要避免踩的 50 个坑1

    最近准备写一些关于golang的技术博文,本文是之前在GitHub上看到的golang技术译文,感觉很有帮助,先给各位读者分享一下. 前言 Go 是一门简单有趣的编程语言,与其他语言一样,在使用时不免 ...

  10. centos 查看硬盘情况

    lsblk                                                                             查看分区和磁盘 df -h     ...