fix: resource cache after finalizer add #1244
Merged
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.
Fix for the following error happens in some cases.
The cause was, that if there are event sources registered and a new resource is created, the finalizer was added, but is was not cached in tempCache, so if an event source produced an event just after, but before the update event from finalizer add arrived, the reconciliation used the resource from the cache without the finalizer (the first version), so controller tried to add the finalizer again.
The fix is actually trivial, just caching the resource to tempCache, as we do at any other update (not patch) operation.