Open dkoshkin opened 4 days ago
This issue is currently awaiting triage.
If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Which of the conditions would you have expected to change?
That being said we're working on new conditions for the next release #11291 I think this will be probably solved through new additional conditions that also contain observedGeneration
What steps did you take and what happened?
Followed the Quick Start for Docker with Kubernetes v1.31.0. Then updated the Cluster object and change the version to v1.31.1.
The
observedGeneration
got updated without any of the conditions changing.Notice the
observedGeneration
is now 4 without any conditions or other status changes.What did you expect to happen?
We rely on a combination of watching for
observedGeneration
to equalgeneration
and then for conditions on the Cluster to beTrue
when determining when a cluster completes an upgrade.In this case though, the
observedGeneration
is updated without any changes in the conditions, which causes a race condition and return prematurely before the upgrade is even started.I would expect for some status to change along with
observedGeneration
that indicates that the spec has changes and needs to be processed.Cluster API version
Kubernetes version
v1.31.0 > v1.31.1
Anything else you would like to add?
We're currently hacked around this using a sleep between changing the resource and starting the wait, but would appreciate some guidance from others who have seen this and have other ideas.
Label(s) to be applied
/kind bug One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.