I've been using external-dns for a while now, but I've run into a frustrating bug where it sometimes deletes all the DNS records it controls for a cluster's Ingresses. Then when it recalibrates, it recreates them, leading to around 2-3 minutes of service disruption. I'm thinking it's time to explore different approaches to managing my DNS records. I'm interested in hearing what tools others are using for this purpose—or if anyone is managing records manually, which sounds painful. Also, I'm swapping my Ingresses for Gateway API's HTTPRoutes, so I'm particularly looking for tools that support both without messing up my records.
1 Answer
I've not used Kubernetes myself, but for our setups, we've integrated DNS records into the same Terraform configuration that manages our deployments. It makes sense to have everything in one place. If you're using Terraform or something similar, you should think about including your DNS config there to streamline the process!
Sounds like the Terraform route is the way to go! I use it along with Ansible for deploying the cluster. It just adds another layer to my deployment process since I currently use Helm for services. But I'm sure it’ll make management a lot smoother in the long run.