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
Currently, we never remove endpoints from the provider when they fail health checks. This is done to prevent NXDomain response. We expect the dns-operator to run in the multicluster environment. This means other controllers could work towards the same root domain and removing endpoints unhealthy endpoints of one of them from the provider might be safe.
What
Consult the DNSRecord.Status.ZoneEndpoints when removing unhealthy records. We want there always to be a chain of endpoints from the root domain to a leaf
How
Two unknowns:
How to prevent multiple controllers from removing the records at the same time (validation before deletion). We could use a TXT record to mark the intention to delete unhealthy and consult that record when making the decision.
Do we need to maintain the tree struct for managing the chain of endpoints? The alternative is just a search for a leaf.
Completed after:
During the removal of endpoints we consult zone endpoints
Added test case for multiple controllers deleting at the same time.
The text was updated successfully, but these errors were encountered:
Why
Currently, we never remove endpoints from the provider when they fail health checks. This is done to prevent NXDomain response. We expect the dns-operator to run in the multicluster environment. This means other controllers could work towards the same root domain and removing endpoints unhealthy endpoints of one of them from the provider might be safe.
What
Consult the
DNSRecord.Status.ZoneEndpoints
when removing unhealthy records. We want there always to be a chain of endpoints from the root domain to a leafHow
Two unknowns:
Completed after:
The text was updated successfully, but these errors were encountered: