<p>I have deployed the Kubernetes dashboard which ended up in   <code>CrashLoopBackOff</code> status. When I run:</p>

<pre><code>$ kubectl logs kubernetes-dashboard-767dc7d4d-mc2sm --namespace=kube-system
</code></pre>

<p>the output is:</p>

<pre><code>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
</code></pre>

<p>How can I fix this? Does this means that the port 10250 isn't open?</p>

<hr>

<p>Update：</p>

<p>@LucaBrasi<br>
<code>Error from server (NotFound): pods "kubernetes-dashboard-767dc7d4d-mc2sm" not found</code></p>

<p><code>systemctl status kubelet --full</code> Output is ：  </p>

<pre><code>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
</code></pre>

<p>Output for <code>kubectl get pods --all-namespaces</code></p>

<p><code>
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
</code></p>

<p>I had the same issue when I reproduced all the steps from the tutorial you've linked - my dashboard was in <code>CrashLoopBackOff</code>state. After I performed this steps and applied new dashboard yaml from the official github documentation (there seems to be no difference from the one you've posted), the dashboard was working properly. </p>

<p>First, list all the objects related to Kubernetes dashboard:</p>

<pre><code>kubectl get secret,sa,role,rolebinding,services,deployments --namespace=kube-system | grep dashboard
</code></pre>

<p>Delete them:</p>

<pre><code>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
</code></pre>

<p>Now apply Kubernetes dashboard yaml:</p>

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

<p>Please tell me if this worked for you as well, and if it did, treat it as a workaround as I don't know the reason yet - I am investigating. </p>
