All the pods seem to be running as normal, and can be reached using kubectl.
All of a sudden (without anyone touching anything), the load balancer is no longer working.
It is not possible to reach the website externally. The internal dns in Kubernetes seems to work as usual however. (When I test by exec-ing into one of the pods)
Does anyone know what might have happened here?
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!
Seems like this was caused by memory usage being too high! I had added ELK for logging a couple of weeks ago, and it had slowly been eating up all the memory.
Somehow this must have killed something critical to external DNS (without actually killing the website pods).
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 AI-native businesses
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.