Kubernetes 仪表板未运行

我已经使用link在ubuntu服务器上安装了kubenertes

然后，我使用以下工具安装了kubernetes仪表板：

kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-rc6/aio/deploy/recommended.yaml

然后我将ClusterIP更改为NodePort 32323，将服务更改为NodePort

但容器没有运行

uday@dockermaster:~$ kubectl -n kubernetes-dashboard get all
NAME                                             READY   STATUS             RESTARTS   AGE
pod/dashboard-metrics-scraper-779f5454cb-pqfrj   1/1     Running            0          50m
pod/kubernetes-dashboard-64686c4bf9-5jkwq        0/1     CrashLoopBackOff   14         50m

NAME                                TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE
service/dashboard-metrics-scraper   ClusterIP   10.103.22.252   <none>        8000/TCP        50m
service/kubernetes-dashboard        NodePort    10.102.48.80    <none>        443:32323/TCP   50m

NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/dashboard-metrics-scraper   1/1     1            1           50m
deployment.apps/kubernetes-dashboard        0/1     1            0           50m

NAME                                                   DESIRED   CURRENT   READY   AGE
replicaset.apps/dashboard-metrics-scraper-779f5454cb   1         1         1       50m
replicaset.apps/kubernetes-dashboard-64686c4bf9        1         1         0       50m

uday@dockermaster:~$ kubectl -n kubernetes-dashboard describe svc kubernetes-dashboard
Name:                     kubernetes-dashboard
Namespace:                kubernetes-dashboard
Labels:                   k8s-app=kubernetes-dashboard
Annotations:              Selector:  k8s-app=kubernetes-dashboard
Type:                     NodePort
IP:                       10.102.48.80
Port:                     <unset>  443/TCP
TargetPort:               8443/TCP
NodePort:                 <unset>  32323/TCP
Endpoints:
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

uday@dockermaster：~$kubectl-n kubernetes仪表板获取所有信息
名称就绪状态重新启动
pod/dashboard-metrics-Slaper-779F54CB-pqfrj 1/1运行0 50m
吊舱/kubernetes-仪表板-64686c4bf9-5jkwq 0/1碰撞回位14 50m
名称类型CLUSTER-IP外部IP端口年龄
服务/仪表板指标刮除器群集IP 10.103.22.252 8000/TCP 50m
服务/kubernetes仪表板节点端口10.102.48.80 443:32323/TCP 50m
姓名就绪最新可用年龄
deployment.apps/dashboard-metrics-scraper 1/1 50m
deployment.apps/kubernetes-dashboard 0/1 1 0 50米
名称所需的当前就绪年龄
replicaset.apps/dashboard-metrics-scraper-779f5454cb 1 50m
replicaset.apps/kubernetes-dashboard-64686c4bf9 1 0 50m
uday@dockermaster：~$kubectl-n kubernetes仪表板描述svc kubernetes仪表板
名称：kubernetes仪表板
名称空间：kubernetes仪表板
标签：k8s app=kubernetes仪表板
注释：选择器：k8s app=kubernetes仪表板
类型：节点端口
IP:10.102.48.80
端口：443/TCP
目标端口：8443/TCP
节点端口：32323/TCP
端点：
会话关联：无
外部流量策略：群集
活动：

---

无论是Tomcat/nginx还是databases，其他应用程序都可以与NodePort配合使用

但在这里，它在容器创建方面失败了

C:\Users\uday\Desktop>kubectl.exe get pods -n kubernetes-dashboard
NAME                                         READY   STATUS             RESTARTS   AGE
dashboard-metrics-scraper-779f5454cb-pqfrj   1/1     Running            1          20h
kubernetes-dashboard-64686c4bf9-g9z2k        0/1     CrashLoopBackOff   84         18h

C:\Users\uday\Desktop>kubectl.exe describe pod kubernetes-dashboard-64686c4bf9-g9z2k -n kubernetes-dashboard
Name:         kubernetes-dashboard-64686c4bf9-g9z2k
Namespace:    kubernetes-dashboard
Priority:     0
Node:         slave-node/10.0.0.6
Start Time:   Sat, 28 Mar 2020 14:16:54 +0000
Labels:       k8s-app=kubernetes-dashboard
              pod-template-hash=64686c4bf9
Annotations:  <none>
Status:       Running
IP:           182.244.1.12
IPs:
  IP:           182.244.1.12
Controlled By:  ReplicaSet/kubernetes-dashboard-64686c4bf9
Containers:
  kubernetes-dashboard:
    Container ID:  docker://470ee8c61998c3c3dda86c58ad17817468f55aa73cd4feecf3b018977ce13ca3
    Image:         kubernetesui/dashboard:v2.0.0-rc6
    Image ID:      docker-pullable://kubernetesui/dashboard@sha256:61f9c378c427a3f8a9643f83baa9f96db1ae1357c67a93b533ae7b36d71c69dc
    Port:          8443/TCP
    Host Port:     0/TCP
    Args:
      --auto-generate-certificates
      --namespace=kubernetes-dashboard
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Sun, 29 Mar 2020 09:01:31 +0000
      Finished:     Sun, 29 Mar 2020 09:02:01 +0000
    Ready:          False
    Restart Count:  84
    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-pzfbl (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  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:
    SizeLimit:  <unset>
  kubernetes-dashboard-token-pzfbl:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  kubernetes-dashboard-token-pzfbl
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  beta.kubernetes.io/os=linux
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
  ----     ------   ----                    ----                 -------
  Warning  BackOff  4m49s (x501 over 123m)  kubelet, slave-node  Back-off restarting failed container

kubectl.exe logs kubernetes-dashboard-64686c4bf9-g9z2k -n kubernetes-dashboard
2020/03/29 09:01:31 Starting overwatch
2020/03/29 09:01:31 Using namespace: kubernetes-dashboard
2020/03/29 09:01:31 Using in-cluster config to connect to apiserver
2020/03/29 09:01:31 Using secret token for csrf signing
2020/03/29 09:01:31 Initializing csrf token from kubernetes-dashboard-csrf secret
panic: Get https://10.96.0.1:443/api/v1/namespaces/kubernetes-dashboard/secrets/kubernetes-dashboard-csrf: dial tcp 10.96.0.1:443: i/o timeout

goroutine 1 [running]:
github.com/kubernetes/dashboard/src/app/backend/client/csrf.(*csrfTokenManager).init(0xc0004e2dc0)
    /home/travis/build/kubernetes/dashboard/src/app/backend/client/csrf/manager.go:40 +0x3b0
github.com/kubernetes/dashboard/src/app/backend/client/csrf.NewCsrfTokenManager(...)
    /home/travis/build/kubernetes/dashboard/src/app/backend/client/csrf/manager.go:65
github.com/kubernetes/dashboard/src/app/backend/client.(*clientManager).initCSRFKey(0xc00043ae80)
    /home/travis/build/kubernetes/dashboard/src/app/backend/client/manager.go:499 +0xc6
github.com/kubernetes/dashboard/src/app/backend/client.(*clientManager).init(0xc00043ae80)
    /home/travis/build/kubernetes/dashboard/src/app/backend/client/manager.go:467 +0x47
github.com/kubernetes/dashboard/src/app/backend/client.NewClientManager(...)
    /home/travis/build/kubernetes/dashboard/src/app/backend/client/manager.go:548
main.main()
    /home/travis/build/kubernetes/dashboard/src/app/backend/dashboard.go:105 +0x20d

C:\Users\uday\Desktop>kubectl.exe获取pods-n kubernetes仪表板
名称就绪状态重新启动
仪表板-metrics-scraper-779f5454cb-pqfrj 1/1运行20小时
kubernetes-dashboard-64686c4bf9-g9z2k 0/1紧急回位84 18h
C:\Users\uday\Desktop>kubectl.exe描述pod kubernetes-dashboard-64686c4bf9-g9z2k-n kubernetes dashboard
名称：kubernetes-dashboard-64686c4bf9-g9z2k
名称空间：kubernetes仪表板
优先级：0
节点：从节点/10.0.0.6
开始时间：2020年3月28日星期六14:16:54+0000
标签：k8s app=kubernetes仪表板
pod模板哈希=64686c4bf9
注释：
状态：正在运行
IP:182.244.1.12
IPs：
IP:182.244.1.12
控制人：ReplicaSet/kubernetes-dashboard-64686c4bf9
容器：
kubernetes仪表板：
容器ID:docker://470ee8c61998c3c3dda86c58ad17817468f55aa73cd4feecf3b018977ce13ca3
图片：kubernetesui/仪表板：v2.0.0-rc6
图像ID:docker-pullable://kubernetesui/dashboard@sha256:61f9c378c427a3f8a9643f83baa9f96db1ae1357c67a93b533ae7b36d71c69dc
端口：8443/TCP
主机端口：0/TCP
Args：
--自动生成证书
--namespace=kubernetes仪表板
国家：等待
原因：仓促退却
最后状态：终止
原因：错误
出境代码：2
开始日期：太阳，2020年3月29日09:01:31+0000
完成日期：太阳，2020年3月29日09:02:01+0000
就绪：错误
重新启动计数：84
活跃度：http get https://:8443/延迟=30s超时=30s周期=10s#成功=1#失败=3
环境：
挂载：
/来自kubernetes仪表板证书（rw）的证书
/来自tmp卷（rw）的tmp
/来自kubernetes仪表盘令牌pzfbl（ro）的var/run/secrets/kubernetes.io/serviceCount
条件：
类型状态
初始化为True
准备错误
集装箱准备好了吗
播客预定为真
卷数：
kubernetes仪表板证书：
类型：Secret（由Secret填充的卷）
SecretName:kubernetes仪表板证书
可选：false
tmp卷：
类型：EmptyDir（共享pod生存期的临时目录）
中等：
SizeLimit：
kubernetes仪表板令牌pzfbl：
类型：Secret（由Secret填充的卷）
秘密名称：kubernetes仪表盘令牌pzfbl
可选：false
QoS等级：最佳努力
节点选择器：beta.kubernetes.io/os=linux
容差：节点角色.kubernetes.io/master:NoSchedule
node.kubernetes.io/not ready:NoExecute持续300秒
node.kubernetes.io/不可访问：不执行300秒
活动：
从消息中键入原因年龄
----     ------   ----                    ----                 -------
警告后退4m49s（x501超过123m）kubelet，从节点后退重新启动失败的容器
kubectl.exe记录kubernetes-dashboard-64686c4bf9-g9z2k-n kubernetes dashboard
2020/03/29 09:01:31开始监控
2020/03/29 09:01:31使用名称空间：kubernetes dashboard
2020/03/29 09:01:31使用群集配置连接到apiserver
2020/03/29 09:01:31使用秘密令牌进行csrf签名
2020/03/29 09:01:31从kubernetes仪表板初始化csrf令牌csrf机密
恐慌：得到https://10.96.0.1:443/api/v1/namespaces/kubernetes-仪表板/secrets/kubernetes仪表板csrf:拨号tcp 10.96.0.1:443:i/o超时
goroutine 1[正在运行]：
github.com/kubernetes/dashboard/src/app/backend/client/csrf.（*csrfTokenManager）.init（0xc0004e2dc0）
/home/travis/build/kubernetes/dashboard/src/app/backend/client/csrf/manager.go:40+0x3b0
github.com/kubernetes/dashboard/src/app/backend/client/csrf.NewCsrfTokenManager（…）
/家/特拉维斯/别尔