Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dnsentry always appends if record already exists in route53 #307

Open
seastranger opened this issue May 17, 2023 · 1 comment
Open

Dnsentry always appends if record already exists in route53 #307

seastranger opened this issue May 17, 2023 · 1 comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@seastranger
Copy link

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

@seastranger seastranger added the kind/enhancement Enhancement, improvement, extension label May 17, 2023
@MartinWeindel
Copy link
Member

@seastranger Can you explain in more detail how your DNSEntry looked like? Did you use routing policies?

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Jan 24, 2024
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

3 participants