doc(cloneset): introduce spec progressDeadlineSeconds #271
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Welcome @MichaelRren! It looks like this is your first PR to openkruise/openkruise.io 🎉 |
| - Scaling down older revisions during upgrade. | ||
| - New Pods are ready or available (satisfying MinReadySeconds condition). | ||
|
|
||
| When the rollout enters the "Progressing" state, the CloneSet controller adds the following condition to the CloneSet's `.status.conditions`: |
There was a problem hiding this comment.
can we summarize various reason for condition Progressing=true in table?
docs/user-manuals/cloneset.md
Outdated
|
|
||
| Therefore, by configuring `.spec.progressDeadlineSeconds`, a CloneSet will traverse multiple states during its lifecycle: | ||
| - Progressing: the rollout is ongoing. | ||
| - Complete: the partition update is successful or the rollout is successful. |
There was a problem hiding this comment.
Complete is neither a reason nor a type, it is not necessary to distinguish complete from progressing
Signed-off-by: michaelrren <[email protected]>
Signed-off-by: michaelrren <[email protected]>
MichaelRren
force-pushed
the
fix-2006
branch
from
e748941 to
5a813bc
Compare
3 participants
No description provided.