Skip to content

Caching status for followup reconciliation and optimistic locking #2798

Closed
@csviri

Description

@csviri

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions