-
Notifications
You must be signed in to change notification settings - Fork 40k
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
kubeadm: reimplement IPVS check #75036
kubeadm: reimplement IPVS check #75036
Conversation
e1e43e7
to
a760d17
Compare
/cc @kad @neolit123 |
a760d17
to
f3e985e
Compare
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.
@bart0sh
thanks for the cleanup. the change LGTM.
please mind that code freeze is tomorrow..
"verify" needs to pass (there is an import-boss issue).
/approve
/priority important-longterm
/test pull-kubernetes-verify |
/test pull-kubernetes-e2e-gce-100-performance |
@neolit123 Thank you for the review. Do you have any idea why import-boss is failing/how to reproduce this? pull-kubernetes-e2e-gce-100-performance failure seems to be not related to this PR. Some testing infra setup issue I guess. |
@bart0sh on a quick look it seems not happy with the new dependency from pkg. |
f3e985e
to
0826e71
Compare
/test pull-kubernetes-integration |
/test pull-kubernetes-verify |
/test pull-kubernetes-e2e-gce-100-performance |
0826e71
to
ea836b5
Compare
@neolit123 thank you for the suggestion! That was exactly it - import-boss was not happy about extra dependencies to the bunch of network-related packages. |
@bart0sh |
ea836b5
to
b04ecbe
Compare
/test pull-kubernetes-e2e-gce |
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.
minor nit, otherwise lgtm
Used existing IPVS Proxier API CanUseIPVSProxier instead of custom implementation. Fixes kubernetes/kubeadm#975
b04ecbe
to
2914171
Compare
/lgtm |
Assigning to approvers for final approval /assign @thokin @m1093782566 @timothysc |
@bart0sh: GitHub didn't allow me to assign the following users: thokin. Note that only kubernetes members and repo collaborators can be assigned and that 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. |
@m1093782566 @timothysc Kindly ping for approval. |
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.
/approve
SGTM on the kubeadm side.
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 for the patch, but I have a comment that I'd like an answer to before lgtm
/approve
/hold
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bart0sh, neolit123, thockin, timothysc 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 |
I think, that this is ready for merge now. Thanks @bart0sh ! |
@bart0sh: The following tests 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. |
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Used existing IPVS Proxier API CanUseIPVSProxier instead
of custom implementation.
Which issue(s) this PR fixes:
Fixes kubernetes/kubeadm#975
Special notes for your reviewer:
This is yet another attempt to correctly fix kubernetes/kubeadm#975 and get rid of huge confusing warning message that scares users.
Does this PR introduce a user-facing change?: