The current behavior is is that the dns.gardener.cloud/dnsnames annotation from multiple DNSAnnotation objects which reference t he same service are not merged. It wins always the newest DNSAnnotation object or the last reconciled one.
Why is this needed:
This can lead to unexpected behavior since only one DNSEntry is created for the last applied object even though multiple DNSAnnotation objects exist for the same service.
What would you like to be added:
The current behavior is is that the
dns.gardener.cloud/dnsnames
annotation from multipleDNSAnnotation
objects which reference t he same service are not merged. It wins always the newestDNSAnnotation
object or the last reconciled one.Why is this needed:
This can lead to unexpected behavior since only one
DNSEntry
is created for the last applied object even though multipleDNSAnnotation
objects exist for the same service.This has been discussed on Slack, see https://kubernetes.slack.com/archives/CB57N0BFG/p1706179077150459. The following example currently leads to having only one
DNSEntry
existing for the referenced service.