Kubernetes仪表板问题

Question

>

Kubectl apply-f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta4/aio/deploy/recomended.yaml

kubectl代理--address=“192.168.56.12”-p 8001-accept-hosts='^*$'

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "no endpoints available for service \"https:kubernetes-dashboard:\"",
  "reason": "ServiceUnavailable",
  "code": 503
}```

Output of a few commands that will required:

[root@k8s-master~]#kubectl logs kubernetes-dashboard-6bb65fcc49-zn2c2-namespace=kubernetes-dashboard

$kubectl get pods -o wide --all-namespaces
NAMESPACE              NAME                                        READY   STATUS             RESTARTS   AGE   IP              NODE      
ATES
kube-system            coredns-5c98db65d4-89c9p                    1/1     Running            0          76m   10.244.0.14     k8s-master
kube-system            coredns-5c98db65d4-ggqfj                    1/1     Running            0          76m   10.244.0.13     k8s-master
kube-system            etcd-k8s-master                             1/1     Running            0          75m   192.168.56.12   k8s-master
kube-system            kube-apiserver-k8s-master                   1/1     Running            0          75m   192.168.56.12   k8s-master
kube-system            kube-controller-manager-k8s-master          1/1     Running            1          75m   192.168.56.12   k8s-master
kube-system            kube-flannel-ds-amd64-74zrn                 1/1     Running            1          74m   192.168.56.14   node1     
kube-system            kube-flannel-ds-amd64-hgcp8                 1/1     Running            0          75m   192.168.56.12   k8s-master
kube-system            kube-proxy-2lczb                            1/1     Running            0          74m   192.168.56.14   node1     
kube-system            kube-proxy-8dxdm                            1/1     Running            0          76m   192.168.56.12   k8s-master
kube-system            kube-scheduler-k8s-master                   1/1     Running            1          75m   192.168.56.12   k8s-master
kubernetes-dashboard   dashboard-metrics-scraper-fb986f88d-d49sw   1/1     Running            0          71m   10.244.1.21     node1     
kubernetes-dashboard   kubernetes-dashboard-6bb65fcc49-7wz6q       0/1     CrashLoopBackOff   18         71m   10.244.1.20     node1     

=========================================

[root@k8s-master ~]# kubectl describe pod kubernetes-dashboard-6bb65fcc49-7wz6q -n kubernetes-dashboard
Name:           kubernetes-dashboard-6bb65fcc49-7wz6q
Namespace:      kubernetes-dashboard
Priority:       0
Node:           node1/192.168.56.14
Start Time:     Mon, 23 Sep 2019 12:56:18 +0530
Labels:         k8s-app=kubernetes-dashboard
                pod-template-hash=6bb65fcc49
Annotations:    <none>
Status:         Running
IP:             10.244.1.20
Controlled By:  ReplicaSet/kubernetes-dashboard-6bb65fcc49
Containers:
  kubernetes-dashboard:
    Container ID:  docker://2cbbbc9b95a43a5242abe13f8178dc589487abcfccaea06ff4be70781f4c3711
    Image:         kubernetesui/dashboard:v2.0.0-beta4
    Image ID:      docker-pullable://docker.io/kubernetesui/dashboard@sha256:a35498beec44376efcf8c4478eebceb57ec3ba39a6579222358a1ebe455ec49e
    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:      Mon, 23 Sep 2019 14:10:27 +0530
      Finished:     Mon, 23 Sep 2019 14:10:28 +0530
    Ready:          False
    Restart Count:  19
    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-q7j4z (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-q7j4z:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  kubernetes-dashboard-token-q7j4z
    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
  ----     ------   ----                       ----            -------
  Warning  BackOff  <invalid> (x354 over 63m)  kubelet, node1  Back-off restarting failed container
[root@k8s-master ~]#

Answer 1

在意识到图表stable/kubernetes-dashboard已经过时之后，我发现您需要应用这个清单：

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

但是，从helm图表迁移到硬编码清单是不可以接受的。经过一番搜索后，相关图表现在位于这个Git repo子文件夹No morestablerepo下，但使用以下内容：

helm repository add kubernetes-dashboard https://kubernetes.github.io/dashboard/
helm install kubernetes-dashboard/kubernetes-dashboard --name my-release

祝你好运！这将修复您的所有问题，因为此图表考虑了所有依赖关系。

null