-
Notifications
You must be signed in to change notification settings - Fork 40.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Wait for kubelet & kube-proxy to be ready on Windows node within 10s #85228
Conversation
Hi @YangLu1031. 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. |
/cc pjh |
/ok-to-test |
/priority important-soon |
/test pull-kubernetes-e2e-windows-gce |
1957d40
to
aa2f538
Compare
/retest |
aa2f538
to
f88ad4a
Compare
/test pull-kubernetes-e2e-windows-gce |
f88ad4a
to
6bc5a18
Compare
/test pull-kubernetes-e2e-windows-gce |
The failing tests all happened in gce-windows-master testgrid as well. Looks like not caused by this PR. |
@pjh Please take another look :) |
6bc5a18
to
0965b57
Compare
/test pull-kubernetes-e2e-windows-gce |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pjh, YangLu1031 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 |
2 similar comments
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
@YangLu1031: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
@pjh can we remove the |
/skip pull-kubernetes-e2e-windows-gce |
/skip |
/milestone v1.17 |
@YangLu1031: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. 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. |
Wait for kubelet & kube-proxy to be ready on Windows node within 10s
Wait for kubelet & kube-proxy to be ready on Windows node within 10s
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Add wait for kubelet & kube-proxy to be ready on windows nodes within 10s. If not, throw exception and exit
Does this PR introduce a user-facing change?: