Question

Kubernetes. Unable to connect to the server

This is the third time when Kubernetes starts to be unavailable for “kubectl”. Sometimes I cannot connect to the cluster using Kubernetes CLI and get the following errors:

Unable to connect to the server: dial tcp x.x.x.x:443: i/o timeout

Or

Unable to connect to the server: net/http: TLS handshake timeout

The indicator near the k8s logo lights yellow whereas it’s green when all Okey. When I try to add extra nodes it stucks in “loading” state without any changes. We rely on your servers and clusters, but it lets us down every week. On your servers, we host production environments of projects and monitoring infrastructure. I cannot Google any information about this issue. What do we do wrong? How to avoid these problems in the future?

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

The same problem. Cluster is not accessible for the last 2 hours. Apps running on cluster are not accessible too.

Managed Kubernetes in DO is not production ready at all :(

As of today is still happening, when installing prometheus-operator chart it loses the connectivity to the cluster to the point where any kubectl command it’s not working.

Even a single kubectl apply -f for a single resource, triggered the connectivity loss to the cluster for more than 2 hours.

And adding nodes to the current pool, took more than 3 hours to complete.

I hope we get more transparency of what is happening with our clusters.

I’ve just experienced this issue for 4-th time and each time I’ve ended up creating a new cluster. I am personally using K8s for my own side-project and it’s still very frustrating even though it isn’t real production yet.

This time the issue started to kick in imminently after I’ve tried to install Kubernetes Monitoring Stack. It never even fully installed, just created Prometheus Operator namespace and its secret. It seems like the issue is somehow related to Prometheus Operator as many others already noticed.

So I’ve googled both of these terms together and found this blog post that I think actually reveals and solves the mystery. And although it intended for GKE it still might help newcomers to deal with this problem.