-
Notifications
You must be signed in to change notification settings - Fork 378
fix: allow non-churn empty nodes to be disrupted (#2206) #2541
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
fix: allow non-churn empty nodes to be disrupted (#2206) #2541
Conversation
|
Hi @AndrewMitchell25. 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-sigs/prow repository. |
fd955e9 to
4bbbc7b
Compare
4bbbc7b to
7fb00ac
Compare
|
/lgtm |
|
/approved |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AndrewMitchell25, jmdeal 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 |
Fixes #N/A
Description
Cherry picks "fix: allow non-churn empty nodes to be disrupted (#2206)" and upgrades golangci-lint (similar to #2485)
How was this change tested?
make toolchainandmake presubmitBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.