Kubernetes dashboard is running but can't reach.

[adalga]

Environment

Dashboard version:  1.7
Kubernetes version: 1.8.7
Operating system: Ubuntu
Node.js version:
Go version:

Steps to reproduce

I am using rancher/rke to create a kubernetes cluster.

./rke up # Creates a kuberenetes cluster
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml
kubectl proxy
and try to reach via http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

Observed result

Error: 'dial tcp 10.233.65.9:8443: getsockopt: connection timed out'
Trying to reach: 'http://10.233.65.9:8443/'

Expected result

Reaching kubernetes dashboard

Comments

kubectl get nodes

NAME STATUS ROLES AGE VERSION
192.168.112.168 Ready etcd,master,worker 48m v1.8.7-rancher1
192.168.112.169 Ready etcd,master,worker 48m v1.8.7-rancher1
192.168.112.171 Ready etcd,master,worker 48m v1.8.7-rancher1

kubectl get pods --all-namespaces

NAMESPACE NAME READY STATUS RESTARTS AGE
default my-nginx 1/1 Running 0 49m
ingress-nginx default-http-backend-66b447d9cf-sdjcq 1/1 Running 0 49m
ingress-nginx nginx-ingress-controller-76h65 1/1 Running 0 49m
ingress-nginx nginx-ingress-controller-8ll4p 1/1 Running 0 49m
ingress-nginx nginx-ingress-controller-9qwtc 1/1 Running 0 49m
kube-system kube-dns-6f7666d48c-zmk4r 3/3 Running 0 49m
kube-system kube-dns-autoscaler-54fd4c549b-226x8 1/1 Running 0 49m
kube-system kube-flannel-2bg4p 2/2 Running 0 49m
kube-system kube-flannel-2zcqn 2/2 Running 0 49m
kube-system kube-flannel-g48kh 2/2 Running 0 49m
kube-system kubernetes-dashboard-747d579ff5-l4kkh 1/1 Running 0 13m

kubectl logs kubernetes-dashboard-747d579ff5-l4kkh -n kube-system

2018/02/22 13:37:04 Using in-cluster config to connect to apiserver
2018/02/22 13:37:04 Using service account token for csrf signing
2018/02/22 13:37:04 No request provided. Skipping authorization
2018/02/22 13:37:04 Starting overwatch
2018/02/22 13:37:04 Successful initial request to the apiserver, version: v1.8.7-rancher1
2018/02/22 13:37:04 Generating JWE encryption key
2018/02/22 13:37:04 New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Starting
2018/02/22 13:37:04 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-system
2018/02/22 13:37:04 Initializing JWE encryption key from synchronized object
2018/02/22 13:37:04 Creating in-cluster Heapster client
2018/02/22 13:37:04 Auto-generating certificates
2018/02/22 13:37:04 Successfuly created and stored certificates
2018/02/22 13:37:04 Serving securely on HTTPS port: 8443
2018/02/22 13:37:04 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.

[floreks]

Error: 'dial tcp 10.233.65.9:8443: getsockopt: connection timed out'
Trying to reach: 'http://10.233.65.9:8443/'

This kind of errors always come from API server, not the application you are trying to reach. Check your cluster config and see if you can access other applications through service proxy first, i.e. grafana. Also I'd recommend using Dashboard 1.8 as 1.7 might not work properly on 1.8 cluster.

[floreks]

Looks like cluster networking issue. Logs from Dashboard container shows that it has started properly. Closing.