Fix FirewallRules concurency issues using a status known LastTransiti… #124
Conversation
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
vincentmrg
force-pushed
the
fix/firewallrules-concurency-reconcile
branch
2 times, most recently
from
68a4236 to
5824fdf
Compare
antonincms
reviewed
Jul 1, 2024
vincentmrg
force-pushed
the
fix/firewallrules-concurency-reconcile
branch
from
5824fdf to
556304f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If a rule LastTransitionTime is before the one stored locally, the cache is not yet aware of a change we made.
To avoid consistency issues, e.g. creating multiples groups for a single node, we requeue.