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
Cherry pick #96876 in controller to 1.20: fix nodelifecyle controller not add NoExecute taint bug #98168
Cherry pick #96876 in controller to 1.20: fix nodelifecyle controller not add NoExecute taint bug #98168
Conversation
…issing fix nodelifecyle controller not add NoExecute taint bug
Hi @CKchen0726. Thanks for your PR. I'm waiting for a kubernetes 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. |
/ok-to-test |
/cc @k82cn @Huang-Wei |
/cc @derekwaynecarr |
@aveshagarwal @smarterclayton @Huang-Wei @k82cn @derekwaynecarr please approve, it's a critical issue. |
/lgtm |
@Huang-Wei: GitHub didn't allow me to assign the following users: gmarek. Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
/approve |
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.
/priority important-soon
/triage accepted
/lgtm
/sig node
I'm going to try to get all three branches lined up.
@ehashman There's no visible option to edit issue/PR labels, so I assumed I can't do it. I'm happy to be wrong on that ;) |
@adampl you can use the bot commands! I don't have the permissions to apply labels directly either. I wrote a guide here for SIG Node: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/triage.md |
@hasheddan can you add |
At the moment this issue has both the /remove-do-not-merge/cherry-pick-not-approved Also, adding /cherry-pick-approved |
@guzmonne a release manager must approve cherry picks. I am reviewing this CP across branches now. |
@hasheddan, oops. Sorry. |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CKchen0726, ehashman, hasheddan, Huang-Wei, k82cn 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 |
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind bug
What this PR does / why we need it:
this PR #89059 try to fix reconcile problem, so every 5s monitorNodeHealth() run processTaintBaseEviction(), add nodes to zoneNoExecuteTainter cause these nodes' status is Unknown or False.
Ref: #96876
Which issue(s) this PR fixes:
Fix: #94183 #96183
Special notes for your reviewer:
I write a helper func to print values inside RateLimitedTimedQueue, and unit test running log as below, and log display the dirty data inside queue field.
Does this PR introduce a user-facing change?