Kubernetes cluster outages

During last day (also some previous days in last weeks) we experienced several outages of Kubernetes cluster which impacted thousands of our clients in PRODUCTION environment.

The situation was monitored by our tech team which noticed that the containers were repeatedly restarted or terminated without our intervention. Our services became unavailable, droplets of cluster were removed from LoadBalancer (had to add them manually over and over again) and totally were not able to get logs of any of running containers (kubectl logs container_name) - following error was received:

Error from server: Get net/http: TLS handshake timeout

The executing of commands inside containers was not working neither (kubectl exec -it container_name sh) - command just got stuck.

When we wanted to access services in cluster (websites, webapps, etc.) from outside we noticed that the request were not forwarded from LoadBalancer to cluster / droplets.

Just adding - we did not change any certificates, nor did any other configuration. Our apps were running without any problem for several days.

Kindly asking you for issue investigating or a statement saying if there were any problems with Kubernetes service / network infrastructure / etc. Thanks

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Same behavior on a cluster, control plane become unavailable, all nodes under Load Balancer “Down” but containers still working and processing jobs.

doctl kubernetes cluster list
ID               Name   Region        Version        Auto Upgrade    Status      Node Pools
some-id    k8s       ams3      1.16.2-do.1             false           degraded    k8s-std k8s-cpu


I’m sorry that I didn’t reply here earlier. I want you to know that we saw this and began discussing it, but I didn’t have anything solid to report until now. This cluster should now be healthy, after several hours of discussion between our engineers. Credit to John K and Nan Z for resolving this, I just wanted to share the news.

Should anyone else find themselves in a similar situation, please don’t hesitate to write to our support team here: