-
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 Node drain documentation #11121
📖 Add Node drain documentation #11121
Conversation
Please ignore the first commit, I'll rebase once the underlying PR merges. |
/assign @fabriziopandini @chrischdi @enxebre |
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.
Great to have this documentation finally!
Two suggestion from my side
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.
Two small improvements for the implementation
docs/book/src/tasks/automated-machine-management/machine_deletions.md
Outdated
Show resolved
Hide resolved
b59fdbc
to
ab25023
Compare
ab25023
to
06fb511
Compare
docs/book/src/tasks/automated-machine-management/machine_deletions.md
Outdated
Show resolved
Hide resolved
9. Machine controller deletes the `BootstrapConfig` object (e.g. `KubeadmConfig`) of the machine and waits until it is gone | ||
10. Machine controller deletes the Node object in the workload cluster | ||
* Node deletion will be retried until either the Node object is gone or `Machine.spec.nodeDeletionTimeout` is expired (`0` means no timeout, but the field defaults to 10s) | ||
|
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 mention node deletion (orthogonally) and volume detach are usually performed by the ccm
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 the first point.
I think for the second: it's CSI and I have the following note above: "* Typically the volumes are getting detached by CSI after the corresponding Pods have been evicted during drain"
Is that fine as is?
/lgtm |
LGTM label has been added. Git tree hash: ef4e5461d7fab209d6ad3c6daa22d7ff4ec2bb94
|
Signed-off-by: Stefan Büringer [email protected]
06fb511
to
1858a75
Compare
/lgtm |
LGTM label has been added. Git tree hash: 8c3c62aaaa0f0e2b8149eddf8d6807441b698b1a
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
/hold cancel |
What this PR does / why we need it:
Adds documentation for Machine deletions and Node drains.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #10056