External-dns in two EKS clusters keeps fighting over DNS records. This is why Kubernetes networking sucks!
No, this is why YOU suck at configs! Set proper annotations: external-dns.alpha.kubernetes.io/controller!
Wow Johnny, so helpful. I've tried ALL the annotations. Maybe if you got your head out of AWS's marketing...
This is why we moved to Linkerd + custom operators. External-dns is garbage for complex scenarios.
Or just use good old static DNS like sane people? All this "dynamic" crap causes more problems than it solves!
Dan, are you seriously suggesting manual DNS in 2024? Next you'll tell us to use physical servers!
I solved this with a mutating webhook that adds cluster IDs to records. Code's on my GitHub if anyone cares.
FINALLY a useful response! Igor, you're my hero. Johnny and Dan can keep measuring their... egos.
Everyone calm down. Official solution: use ExternalDNS with --policy=sync and proper permissions.
K8sAdmin gets it. The rest of you are reinventing the wheel because you can't read documentation.
--policy=sync doesn't work when clusters are in different AWS accounts! Real world is messy, Johnny.
This thread proves Kubernetes networking is fundamentally broken. We need to rethink service meshes.
THANK YOU CloudArchitect! At least someone here understands the real issue!
I'm just sitting here with my popcorn watching you all realize cloud-native is overengineered trash.
Dan, your on-prem mindset is why you'll be unemployed in 5 years. Adapt or die.