Ignore time in ManagedFields when processing events from dependent resources #59
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 the change:
Ignores time in ManagedFields when determining whether events should be skipped. This gets us back the behavior we had before managedFields were added, as when the kubelet updates the resourceVersion it also updates the time in its managedFields entry.
Motivation for the change:
We've had users reporting infinite reconciliation and this is likely the culprit.
Fixes operator-framework/operator-sdk#3950
Fixes operator-framework/operator-sdk#4258