Skip to content

Manage observed generation in condition manager #149

@simontesar

Description

@simontesar

Currently the condition manager does not set the observed generation of a condition. This prevents a caller from comparing a resource's generation with a condition's observed generation, i.e. ensuring that a condition is not stale but valid for a given spec.

Adjust the ConditionManager to always set the condition's observedGeneration to the resource's .metadata.generation when setting a condition on a resource's status. This should be the default behaviour.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions