-
Notifications
You must be signed in to change notification settings - Fork 39
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
Wait for replica to update pods before processing next statefulset update #260
Conversation
Codecov Report
@@ Coverage Diff @@
## master #260 +/- ##
==========================================
- Coverage 75.54% 75.45% -0.09%
==========================================
Files 31 31
Lines 2437 2310 -127
==========================================
- Hits 1841 1743 -98
+ Misses 444 425 -19
+ Partials 152 142 -10 Continue to review full report at Codecov.
|
simulatePodsNotUpdated: true, | ||
expUpdateStatefulSets: []string{"cluster1-rep0", "cluster1-rep1", "cluster1-rep2"}, | ||
expFailedUpdateStatefulSets: []string{"cluster1-rep1", "cluster1-rep2"}, | ||
expNotDone: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for my own understanding: this would be false before your change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wesleyk it was more that, before this change if simulatePodsNotUpdated
had existed in this test code and the "UpdatedReplicas" did not match the expected replicas in the statefulset it would have progressed to update the next statefulset anyway.
This allows for gating progression to updating the next statefulset until all pods have been updated, avoiding the statefulset looking "ready" and "healthy" even though it has a pending update which it's about to process (and start updating pods).