Skip to content

Caching status for followup reconciliation and optimistic locking #2798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
csviri opened this issue May 14, 2025 · 0 comments · Fixed by #2800
Closed

Caching status for followup reconciliation and optimistic locking #2798

csviri opened this issue May 14, 2025 · 0 comments · Fixed by #2800
Milestone

Comments

@csviri
Copy link
Collaborator

csviri commented May 14, 2025

PrimaryUpdateAndCacheUtils now does not support status patching with optimistic locking, since when we are want to store an allocated value in statues, we want to have that value always stored.

An another approach would be with optimistic locking is to retry if it fails, and re-reading the resource - apply the changes and apply again.

Note that the nice part about this that this way, we don't have to set parseResourceVersionsForEventFilteringAndCaching true to have this work in all cases properly, on the other hand having a correct number of retries is theoretically tricky, but in practice this should work fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant