I've been relying on external-dns for my Kubernetes deployments, but I've hit a snag lately where it's randomly deleting all records tied to my Ingresses and then recreating them a few minutes later, causing service disruptions. This has me thinking it might be time to reevaluate how I manage DNS records. I'm curious about the methods and tools others use to handle this – are you using any specific tools, or do you just manage everything manually? That sounds pretty tedious! I should mention I'm also transitioning from Ingresses to Gateway API's HTTPRoutes, so it would be great to find a solution that supports both without messing up my records.
1 Answer
While I don't use Kubernetes myself, I've integrated the DNS records for my deployments directly into my Terraform configuration. It keeps everything in one place and manages the lifecycle of resources, including DNS. If you’re not using Terraform already, you might want to consider why not? It could simplify your setup a lot!
I was thinking about moving to Terraform. It just seems like it would add another layer to my deployment process, especially since I use Helm for most of my services.