-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
Windows node graceful shutdown #127404
Windows node graceful shutdown #127404
Conversation
Hi @zylxjtu. 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-sigs/prow repository. |
/ok-to-test |
@@ -21,7 +21,9 @@ package service | |||
|
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 would suggest to put an OWNERS file in this directlory so SIG Windows can approve it.
If you do so, please also include SIG Node team as approvers
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.
thanks, this is also what we discussed before, let me check with @marosset and @jsturtevant
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.
Please make sure to add Node reviewers and approvers into that file since it will be Node-related code. I don't think we should block every change in this file by pkg/
approvers.
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 Owner file @SergeyKanzhelev
pkg/windows/service/OWNERS
Outdated
|
||
approvers: | ||
- sig-windows-api-reviewers | ||
- mrunalp |
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.
use alias sig-node-approvers
instead of explicit names
pkg/windows/service/OWNERS
Outdated
# See the OWNERS docs at https://go.k8s.io/owners | ||
|
||
approvers: | ||
- sig-windows-api-reviewers |
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.
why reviewers have approvals permission? Is it intentional?
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.
Let's move all the edits to the OWNERS file out to a seperate PR
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 didn't expect it will be such a struggle. I am OK with the separate PR
- SergeyKanzhelev | ||
reviewers: | ||
- sig-windows-api-reviewers | ||
- sig-node-reviewers |
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.
also add labels:
- sig-node-reviewers | |
- sig-node-reviewers | |
labels: | |
- sig/windows | |
- sig/node |
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
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.
thx. I suggest just do sig-node-approvers as suggested above and merge it already. We can add Windows approvers later
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.
updated
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.
pls remove sig-windows-api-reviewers
from approvers
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.
updated
/retest |
pkg/windows/service/OWNERS
Outdated
- sig-windows-api-reviewers | ||
- mrunalp | ||
- kannon92 | ||
- pacoxu | ||
- SergeyKanzhelev |
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.
- sig-windows-api-reviewers | |
- mrunalp | |
- kannon92 | |
- pacoxu | |
- SergeyKanzhelev | |
- sig-node-approvers |
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.
@marosset anybody from wig windows explicitly?
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
LGTM label has been added. Git tree hash: b7290c6f6d51736b31fe10bff66ab7f2b92bb5aa
|
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, marosset, SergeyKanzhelev, zylxjtu 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-required |
/retest |
1 similar comment
/retest |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This is to implement the windows node shutdown, which is proposed in here:
kubernetes/enhancements#4813
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: