-
Notifications
You must be signed in to change notification settings - Fork 264
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
WS 2004 supports dual stack #1003
Conversation
@dcantah @katiewasnothere @daschott any ideas if this is correct or if certain patch releases in hns v11 don't support dualstack? |
@jsturtevant I'm not sure. Paging @elweb9858 as she's helped me understand the HNS versioning madness before |
@kumarvin123 was it intentional that HNS version 11 was not included in the supported versions here ? |
310d3fd
to
0882cf3
Compare
Based on some conversations we've identified that WS 2004+ supports dualstack and that corresponds to HNS v11.10+. 10.5 corresponds to 19H2 which doesn't have full support |
Related work items: microsoft#388, microsoft#389, microsoft#393, microsoft#394, microsoft#395, microsoft#396, microsoft#397, microsoft#398, microsoft#399, microsoft#400, microsoft#401, microsoft#402, microsoft#403, microsoft#404, microsoft#405, microsoft#931, microsoft#973, microsoft#1001, microsoft#1003, microsoft#1004, microsoft#1005, microsoft#1006, microsoft#1007, microsoft#1009, microsoft#1010, microsoft#1012, microsoft#1013, microsoft#1014, microsoft#1015, microsoft#1016, microsoft#1017, microsoft#1019, microsoft#1021, microsoft#1022, microsoft#1024, microsoft#1025, microsoft#1027, microsoft#1028, microsoft#1029, microsoft#1030, microsoft#1031, microsoft#1033
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>
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>
…ning WS 2004 supports dual stack
While working on kubernetes/kubernetes#101047 I found that WS 2004 is not being shown as support.
Docs state: 2004 (kernel version 10.0.19041.610)
I added custom logging to kubeproxy which showed I was on version
11
of HNS on10.0.19041
I am not sure how HNS versions map to WS versions. Maybe there are minor versions of 2004 that don't support it?