introduce dns.gardener.cloud/target-hard-ignore
annotation
#404
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
If source controller creates a
DNSEntry
in the target cluster, it is not possible to set thedns.gardener.cloud/ignore
annotation on the createdDNSEntry
. It is overwritten by the source controller to keep it in-sync with the source object.Therefore a second annotation is introduced
dns.gardener.cloud/target-hard-ignore
with the similar behaviour. Additionally, the deletion of theDNSEntry
is also ignored to make usage future-proof if there are noDNSOwners
anymore.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: