fix: Sink IsConflict error when updating IMC/MC status #300
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes
Both the fleet-member-agent and the fleet-member-net-controller-manager will update the
IMC object in the hub cluster to update the heartbeat information at every 60 seconds. If the updates
from two controllers are somehow in-sync, one of them can hit the update conflict error.
There is not ideal way to avoid update conflicts since they are two controllers running in two different Pods.
Hence this change chooses to sink the update conflict error because
How has this code been tested
Manual test
Special notes for your reviewer