Open benbouillet opened 2 months ago
I'd love to rollout external-dns at work but I'm running into the same roadblock. Maybe something like an optional flag to configure external-dns to ignore records where the name and target already match could help here?
What would you like to be added:
We'd like external-dns to be able to manage DNS record for multiple Istio virtualservices behind an Istio gateway with a wildcard hostname configuration. As of now, if the hostname configuration is delegated to the virtualservices (ie. the Gateway is configured with a wildcard hostname, and virtualservices manages multiple paths on one hostname) , external-dns will loop over the virtualservice and endlessly try to update the DNS records
Why is this needed: SRE team here, we'd like to avoid managing the DNS records for each new API/app release, so the gateway is configured this way:
The associated virtualservice are configured this way:
As hosts are defined at the
virtualservice
level (and as"*"
at thegateway
level), we configured the sources as following in theexternal-dns
helm chart:When deploying
external-dns
, looping on eachvirtualservice
, eachvirtualservice
wants to manage the DNS entry and rewrite the previous one: