Kubernetes 仪表板 CrashLoopBackOff，出现错误 "connect: no route to host"，我该如何解决？

Question

我已经部署了 Kubernetes 仪表板，它最终处于 CrashLoopBackOff 状态。当我运行:

$ kubectl logs kubernetes-dashboard-767dc7d4d-mc2sm --namespace=kube-system

输出是：

Error from server: Get https://10.4.211.53:10250/containerLogs/kube-system/kubernetes-dashboard-767dc7d4d-mc2sm/kubernetes-dashboard: dial tcp 10.4.211.53:10250: connect: no route to host

我该如何解决这个问题？这是否意味着端口 10250 未打开？

更新：

@LucaBrasi
Error from server (NotFound): pods "kubernetes-dashboard-767dc7d4d-mc2sm" not found

systemctl status kubelet --full输出为：

kubelet.service - kubelet: The Kubernetes Node Agent
   Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/kubelet.service.d
           └─10-kubeadm.conf
   Active: active (running) since 一 2018-09-10 15:04:57 CST; 1 day 23h ago
     Docs: https://kubernetes.io/docs/
 Main PID: 93440 (kubelet)
    Tasks: 21
   Memory: 78.9M
   CGroup: /system.slice/kubelet.service
           └─93440 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup-driver=cgroupfs --cni-bin-dir=/opt/cni/bin --cni-conf-dir=/etc/cni/net.d --network-plugin=cni

kubectl get pods --all-namespaces

的输出

NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-78fcdf6894-qh6zb 1/1 Running 2 3d kube-system coredns-78fcdf6894-xbzgn 1/1 Running 1 3d kube-system etcd-twsr-whtestserver01.garenanet.com 1/1 Running 2 3d kube-system kube-apiserver-twsr-whtestserver01.garenanet.com 1/1 Running 2 3d kube-system kube-controller-manager-twsr-whtestserver01.garenanet.com 1/1 Running 2 3d kube-system kube-flannel-ds-amd64-2bnmx 1/1 Running 3 3d kube-system kube-flannel-ds-amd64-r58j6 1/1 Running 0 3d kube-system kube-flannel-ds-amd64-wq6ls 1/1 Running 0 3d kube-system kube-proxy-ds7lg 1/1 Running 0 3d kube-system kube-proxy-fx46d 1/1 Running 0 3d kube-system kube-proxy-ph7qq 1/1 Running 2 3d kube-system kube-scheduler-twsr-whtestserver01.garenanet.com 1/1 Running 1 3d kube-system kubernetes-dashboard-767dc7d4d-mc2sm 0/1 CrashLoopBackOff 877 3d

Answer 1

我在重现您链接的教程中的所有步骤时遇到了同样的问题 - 我的仪表板处于 CrashLoopBackOff 状态。在我执行了这些步骤并应用了官方 github 文档中的新仪表板 yaml 之后（似乎与您发布的那个没有区别），仪表板工作正常。

首先，列出与 Kubernetes 仪表板相关的所有对象：

kubectl get secret,sa,role,rolebinding,services,deployments --namespace=kube-system | grep dashboard

删除它们：

kubectl delete deployment kubernetes-dashboard --namespace=kube-system 
kubectl delete service kubernetes-dashboard  --namespace=kube-system 
kubectl delete role kubernetes-dashboard-minimal --namespace=kube-system 
kubectl delete rolebinding kubernetes-dashboard-minimal --namespace=kube-system
kubectl delete sa kubernetes-dashboard --namespace=kube-system 
kubectl delete secret kubernetes-dashboard-certs --namespace=kube-system
kubectl delete secret kubernetes-dashboard-key-holder --namespace=kube-system

现在应用 Kubernetes 仪表板 yaml：

kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml

请告诉我这是否也适用于您，如果适用，请将其视为解决方法，因为我还不知道原因 - 我正在调查。

Kubernetes 仪表板 CrashLoopBackOff，出现错误 "connect: no route to host"，我该如何解决？

Kubernetes Dashboard CrashLoopBackOff, Get error "connect: no route to host", How could I fix it?

kubernetes

kubernetes-dashboard