You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
% k get virtualservice -A
NAMESPACE NAME GATEWAYS HOSTS AGE
apps service1 ["gateway-api"] ["api.ourdomain.com"] 80d
apps service2 ["gateway-api"] ["api.ourdomain.com"] 80d
apps service3 ["gateway-api"] ["api.ourdomain.com"] 80d
As hosts are defined at the virtualservice level (and as "*" at the gateway level), we configured the sources as following in the external-dns helm chart:
sources:
- istio-virtualservice
- ingress
When deploying external-dns, looping on each virtualservice, each virtualservice wants to manage the DNS entry and rewrite the previous one:
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:The text was updated successfully, but these errors were encountered: