You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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
): external-dns:0.13.2-debian-11-r0The text was updated successfully, but these errors were encountered: