f5 node watch fix - needs a cache to process 'MODIFY' events #11742
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.
Poor code before, never accounted that nodes that were already created before F5 is launched will only get a MODIFIED event. This code takes care of that (and ignores the subsequent MODIFY events caused by status updates).
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1389706
@pravisankar Please review. Thanks for the hint.
cc @openshift/networking