-
Notifications
You must be signed in to change notification settings - Fork 38.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
Replace custom dualstack support logic in Windows Kube-proxy #104952
Conversation
Hi @dcantah. 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. |
/sig windows |
@jayunit100 do you want to take a look? |
/ok-to-test |
Can we add the min version of hcsshim that properly handles version range checks to the comments in the PR? |
@marosset Sure! |
b06d48b
to
2b9dea2
Compare
@marosset Done! |
/lgtm |
@elweb9858 @jayunit100 Anyone able to give this a look? |
Due to an incorrect version range definition in hcsshim for dualstack support, the Windows kubeproxy had to define it's own version range logic to check if dualstack was supported on the host. This was remedied in hcsshim (microsoft/hcsshim#1003) and this work has been vendored into K8s as well (kubernetes#104880). This change simply makes use of the now correct version range to check if dualstack is supported, and gets rid of the old custom logic. Signed-off-by: Daniel Canter <dcanter@microsoft.com>
2b9dea2
to
ce52f70
Compare
/triage accepted |
/lgtm @sbangari for approval |
/lgtm |
/approve |
@dcantah Thanks for cleaning this up! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dcantah, sbangari 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Due to an incorrect version range definition in hcsshim for dualstack support, the Windows kube-proxy had to define its own version range logic to check if dualstack was supported on the host. This was remedied in hcsshim (microsoft/hcsshim#1003) and this work has been vendored into K8s as well (#104880). This change simply makes use of the now correct version range to check if dual stack is supported, and gets rid of the old custom logic.
cc @marosset @sbangari
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.: