-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
📖 Add CAPI book section on clusterctl alpha rollout
#4328
📖 Add CAPI book section on clusterctl alpha rollout
#4328
Conversation
Hi @Arvinderpal. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/milestone v0.4.0 |
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.
overall lgtm, only few nits
|
||
### Restart | ||
|
||
Use the `restart` sub-command to force an immediate rollout. For example, here the MchineDeployment `my-md-0` will be immediately rolled out: |
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.
Should we add a note explaining what rollout means: deleting machines (including cordon/drain of workloads), recreating new ones according to maxUnavailable/maxSurge
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.
Done.
|
||
### Undo | ||
|
||
Use the `undo` sub-command to rollback to an ealier revision. For example, here the MachineDeployment `my-md-0` will be rolled back to revison number 3. If the `--to-revision` flag is omited, the MachineDeployment will be rolled back to the revision immediately preceding the current one. |
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.
should we document what happen if the requested revision/the immediate preceding revision does not exists?
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.
Added: "If the desired revision does not exist, the undo will return an error."
|
||
### Pause/Resume | ||
|
||
Use the `pause` sub-command to pause a Cluster API resource. |
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.
Should we document what happens if if are pausing an already paused rollout (or if we are unpausing something not currently paused)
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.
Done
|
||
<h1> Warning </h1> | ||
|
||
Paused resources will not be reconciled by a controller. By resuming a resource, we allow it to be reconciled again. |
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.
Are we using paused at object level or machineDeployments.spec.Paused?
In case we are using the first, should we document that pausing could imply also some undesired side effects because nothing gets updated, including e.g. the ObservedGeneration, replica counters etc.
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.
I added this comment: "Note that internally, this command sets the Paused
field within the resource spec (e.g. MachineDeployment.Spec.Paused) to 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.
Overall looks good, really like the idea and also +1 to the idea if we can make this to work in kubectl!
There are few nits, please see below:
@@ -0,0 +1,51 @@ | |||
# clusterctl alpha rollout | |||
|
|||
The `clusterctl alpha rollout` command manages the rollout of a cluster-api resource. It consists of several sub-commands which are documented below. |
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.
maybe we should make cluster-api OR Cluster API
word consistent throughout this document? (Cluster API
seems to be more frequently used in the repo)
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.
Using Cluster API
now.
@Arvinderpal Are you able to address the comments above? |
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.
@fabriziopandini @furkatgofurov7 I addressed your comments. PTAL
@@ -0,0 +1,51 @@ | |||
# clusterctl alpha rollout | |||
|
|||
The `clusterctl alpha rollout` command manages the rollout of a cluster-api resource. It consists of several sub-commands which are documented below. |
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.
Using Cluster API
now.
|
||
### Restart | ||
|
||
Use the `restart` sub-command to force an immediate rollout. For example, here the MchineDeployment `my-md-0` will be immediately rolled out: |
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.
Done.
|
||
### Undo | ||
|
||
Use the `undo` sub-command to rollback to an ealier revision. For example, here the MachineDeployment `my-md-0` will be rolled back to revison number 3. If the `--to-revision` flag is omited, the MachineDeployment will be rolled back to the revision immediately preceding the current one. |
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.
Added: "If the desired revision does not exist, the undo will return an error."
|
||
### Pause/Resume | ||
|
||
Use the `pause` sub-command to pause a Cluster API resource. |
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.
Done
|
||
<h1> Warning </h1> | ||
|
||
Paused resources will not be reconciled by a controller. By resuming a resource, we allow it to be reconciled again. |
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.
I added this comment: "Note that internally, this command sets the Paused
field within the resource spec (e.g. MachineDeployment.Spec.Paused) to true."
a1e0e24
to
b323861
Compare
@vincepri I just did. PTAL |
/retest |
/lgtm |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: detiber The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-cluster-api-test-main |
What this PR does / why we need it:
Documents the
clusterctl alpha rollout
feature.Related Issue:
#3439