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?
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.
×
Did anyone find a solution to this? I am having the exact issue with one of my clusters today.
I’m having this issue as well. Not with anything crazy or particularly API heavy. I can’t imagine what would be causing these kinds of problems. I’ve enabled auto-scaling on my pool and all its running is a proxy and monitoring.
Woke up to an alert from a service that I can’t access thanks to this issue. Kubectl just times out making a request, as does ping (!). No indication of any issue on DO’s status site or dashboard (not including the k8s-built dashboard, which, surprise!, can’t connect). It seems to be completely out of my hands.
I haven’t touched any k8s config in months, this is completely out of the blue. Node metrics are happy, and thankfully things remain up, but to say I am concerned about the stability of my production kubernetes hosting would be an understatement.