-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Simplify usage of pre-remove role #8334
Simplify usage of pre-remove role #8334
Conversation
- Use builtin task scheduling of ansible (same task on each host) instead of manual looping on master Benefits: - One less play in remove-node.yml playbook - Parralel node drain - Drain parameters (timeout, grace period, retries, allow_ungraceful_removal) can be adjusted separately for each node with ansible variables
Hi @VannTen. 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. |
This also accomplishes the same purpose than #8099 without needing ansible 2.11 |
Nice improvement @VannTen ! /ok-to-test |
/lgtm |
/cc @floryut - this could make it into 2.18 |
Fine by me 👍 |
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.
@VannTen Thanks
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, VannTen 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 |
- Use builtin task scheduling of ansible (same task on each host) instead of manual looping on master Benefits: - One less play in remove-node.yml playbook - Parralel node drain - Drain parameters (timeout, grace period, retries, allow_ungraceful_removal) can be adjusted separately for each node with ansible variables
- Use builtin task scheduling of ansible (same task on each host) instead of manual looping on master Benefits: - One less play in remove-node.yml playbook - Parralel node drain - Drain parameters (timeout, grace period, retries, allow_ungraceful_removal) can be adjusted separately for each node with ansible variables
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
instead of manual looping on master
Benefits:
allow_ungraceful_removal) can be adjusted separately for each node
with ansible variables
Which issue(s) this PR fixes:
None
Does this PR introduce a user-facing change?: