External DNS controller does not sync records as expected

[nitinkeswani]

What happened:
We have setup the external dns controller in our aws eks cluster. We created a simple A record using dnsendpoint crd.
The A record did get created in the route 53 hosted zone along with some txt records. However if i delete just the A record(Keeping the associated txt records in place), the external dns controller does not re-create the A record to bring the records back to the desired state.
If i delete all the records (A and associated txt records), then it does recreate the entire set again

What you expected to happen:
I was hoping the external dns controller would always sync the records and keep them in the desired state irrespective of which records are deleted

Environment:

• External-DNS version (use external-dns --version): external-dns:0.13.2-debian-11-r0
• DNS provider: AWS Route 53
• Others:

[stanislavzaletskyi]

hey , try policy: sync

external-dns/charts/external-dns/values.yaml

Line 212 in fe2924b

policy: upsert-only

FYI: be carefull it will remove all records in zone , which are not detected in services/ingresses by external-dns

[ivankatliarchuk]

/area provider/aws
/help

[k8s-ci-robot]

@ivankatliarchuk:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/area provider/aws
/help

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-sigs/prow repository.