Question
How to get to work Dashboard and Helm in DO K8s cluster?
- Posted October 3, 2018
- KubernetesDebian
Hello. I’ve created new k8s cluster with DigitalOcean. And there are few things I cannot figure out how to solve:
- kubectl shows that Dashboard pod is deployed, its service is ready to serve. With kubeclt proxy I managed to try to load dashboard via browser:
Error: 'dial tcp 10.244.5.3:8443: i/o timeout'
Trying to reach: 'https://10.244.5.3:8443/'
- With helm init I tried to install helm to cluster. And after that I can see that tiller-deploy pod is running. But with helm version I’ve got errror:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Error: forwarding ports: error upgrading connection: error dialing backend: dial tcp 10.131.80.172:10250: connect: no route to host
Same error with helm install stable/nginx-ingress
Looks like in both cases I cannot connect to cluster private network IPs. Any ideas how to solve it? Thanks in advance.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hey there,
It looks like you (and the others reporting the issue in the comments) may have ran into an issue with the Kubernetes master node not being properly assigned to your private network.
We’re working to resolve this now.
Had the same kind of issue twice tonight, deploying traefik in Kubernetes NYC
Just discovered: deleting k8s cluster will not delete your load balancers that were made when type=LoadBalancer services were deployed. I don’t know if it’s a bug or feature :) Digitalocean-cloud-controller-manager usually deletes load balancer right after you delete deployed service.
It doesn’t work so far, in kubctl proxy I see:
I1003 19:15:27.825295 47342 logs.go:41] http: proxy error: context canceled
I1003 19:15:33.511797 47342 logs.go:41] http: proxy error: context canceled
I1003 19:15:49.507189 47342 logs.go:41] http: proxy error: context canceled
I1003 19:16:19.680289 47342 logs.go:41] http: proxy error: dial tcp 192.168.99.100:8443: i/o timeout
I1003 19:16:58.140826 47342 logs.go:41] http: proxy error: dial tcp 192.168.99.100:8443: i/o timeout
I1003 19:17:14.335255 47342 logs.go:41] http: proxy error: dial tcp 192.168.99.100:8443: i/o timeout
I1003 19:17:52.565512 47342 logs.go:41] http: proxy error: dial tcp 192.168.99.100:8443: i/o timeout
I1003 19:18:07.954353 47342 logs.go:41] http: proxy error: dial tcp 192.168.99.100:8443: i/o timeout
and no dashboard in browser. I’ll create new cluster and try again.
We’ve resolved the issue that was impacting Kubernetes clusters in regions that weren’t NYC1 and FRA1- everything should be behaving as expected. If you’re still experiencing any issues, please feel free to open up a support ticket so that we can investigate!
At the moment we’re working to resolve an issue with Kubernetes clusters in regions that are not NYC1 & FRA1.
As an immediate resolution, you can redeploy your cluster to one of those two regions, while we fix the underlying problem.
This comment has been deleted
I’ve got the exact same issue with dashboard & the the logs.
Same here… Also there is quite same problem with logs:
Trying to get the pod logs: