-
Notifications
You must be signed in to change notification settings - Fork 35
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Handle transient ServiceImport delete in the resolver
During DR testing where the broker cluster is recovered from a backup, it was observed that the coredns plugin resolver received a ServiceImport delete event followed by an add event while the EndpointSlice remained. This resulted in failed DNS queries b/c the service info was removed. The assumption is that a ServiceImport deletion means the service was unexported, which is normally the case. However, during DR scenarios, transient deletions may occur due to reconciliation on LH agent startup if it observes a local copy of a remote resource doesn't yet exist on the broker due to timing. When this occurs a restart of the coredns pod is required to correct it. To alleviate this issue, make the resolver more resilient by only removing the service info data when there's no more cluster data, ie when all the cluster EndpointSlices are deleted. Normally, on unexport, the EndpointSlices are deleted after the aggregated ServiceImport is deleted. Signed-off-by: Tom Pantelis <[email protected]>
- Loading branch information
Showing
4 changed files
with
30 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters