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
Is your feature request related to a problem? Please describe.
With the changes made for compatibility between Avi Essential and external-dns it's not possible to use DNS with L4 unless autoFQDN is enabled.
DNS on L4 and automatic FQDN shouldn't be configured together. There are many use cases for DNS on L4 without enabling autoFQDN on every service.
Describe the solution you'd like
Create a method for users to create a DNS entry for L4 services without automatically creating it for every service. This could be another option for autoFQDN, or using a different annotation to external-dns.alpha.kubernetes.io/hostname.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
The use case is to create a DNS entry for services of type LoadBalancer without having an entry created for every load balancer. This may be because clusters share the default domain, or the scheme used by default or flat are incompatible. It will use existing logic in the application to create the DNS entry without needing to manually create the entry or use additional tools.
Is your feature request related to a problem? Please describe.
With the changes made for compatibility between Avi Essential and external-dns it's not possible to use DNS with L4 unless
autoFQDN
is enabled.DNS on L4 and automatic FQDN shouldn't be configured together. There are many use cases for DNS on L4 without enabling autoFQDN on every service.
Describe the solution you'd like
Create a method for users to create a DNS entry for L4 services without automatically creating it for every service. This could be another option for autoFQDN, or using a different annotation to external-dns.alpha.kubernetes.io/hostname.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: