Dnsentry always appends if record already exists in route53 #307
Labels
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
Dnsentry appends a new mapping instead of replacing it:
if for some reason dnsentry was force deleted (without controller handling the removal in route53)
and then recreated with a different mapping, the existing mapping is not replaced, but appended to:
so if the old entry was pointing to ip1 and the new entry points to ip2, the result will be record containing both ip's.
can this behavior be changed / controlled somehow when i create the dnsentry?
Thanks in advance
The text was updated successfully, but these errors were encountered: