By OlegOfren
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.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
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.
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!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.