DNS Record Conflict Stops Update After Batch Update is Applied

[lkusnadi]

After #1164, I found that if you have a record that is defined in the external dns annotation with conflict, it can stop the entire update of DNS record. This is because the update is batched and if a conflict is detected within the batch, the process will not proceed.

This causes backlog of update requests queuing in external DNS.

If there's a conflict (e.g. the DNS record has been created by something else, other than external DNS), external DNS must first check if it has a corresponding TXT record. If it doesn't, it shouldn't be included in the batch; therefore the clog will not happen.

Wondering if anyone encounter this issue and what's the workaround if any? Thank you.

[richstokes]

Same issue with me - #1517

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[seanmalloy]

/kind bug
/triage duplicate
/close

This is a duplicate of #1517.

[k8s-ci-robot]

@seanmalloy: Closing this issue.

In response to this:

/kind bug
/triage duplicate
/close

This is a duplicate of #1517.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.