Skip to content

reconcile: properly check deployment and statefulset ready status#1588

Merged
f41gh7 merged 1 commit intomasterfrom
gh-1579
Oct 30, 2025
Merged

reconcile: properly check deployment and statefulset ready status#1588
f41gh7 merged 1 commit intomasterfrom
gh-1579

Conversation

@f41gh7
Copy link
Collaborator

@f41gh7 f41gh7 commented Oct 30, 2025

Previously, due to race condition between local client cache and actual
Kubernetes api-server, operator may incorrectly track ready status for
Deployment and StatefulSet.

client.Update(object) call increments Generation field of the update
object if there was any change. While, client.Get(object) may not yet have this change.

So this commit explicitly checks if updateObject.Generation is greater
than getObject.Generation, to prevent such case.

Fixes #1579

 Previously, due to race condition between local client cache and actual
 Kubernetes api-server, operator may incorrectly track ready status for
 Deployment and StatefulSet.

 client.Update(object) call increments `Generation` field of the update
object if there was any change. While, client.Get(object) may not yet
have this change.

 So this commit explicitly checks if updateObject.Generation is greater
 than getObject.Generation, to prevent such case.

Fixes #1579
@f41gh7 f41gh7 merged commit 698e7f1 into master Oct 30, 2025
4 of 6 checks passed
@f41gh7 f41gh7 deleted the gh-1579 branch October 30, 2025 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feature request: configurable rollout strategy for vmcluster

2 participants