Skip to content
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

Merged
merged 1 commit into from
May 5, 2021

Conversation

jsturtevant
Copy link
Contributor

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)

cmd /c ver

Microsoft Windows [Version 10.0.19041.867]

I added custom logging to kubeproxy which showed I was on version 11 of HNS on 10.0.19041

I0414 22:35:15.143135    3372 proxier.go:202] hns version%!(EXTRA hcn.Version={11 10})                    

I am not sure how HNS versions map to WS versions. Maybe there are minor versions of 2004 that don't support it?

@jsturtevant
Copy link
Contributor Author

@dcantah @katiewasnothere @daschott any ideas if this is correct or if certain patch releases in hns v11 don't support dualstack?

@dcantah
Copy link
Contributor

dcantah commented Apr 19, 2021

@jsturtevant I'm not sure. Paging @elweb9858 as she's helped me understand the HNS versioning madness before

@elweb9858
Copy link
Contributor

@kumarvin123 was it intentional that HNS version 11 was not included in the supported versions here ?

@jsturtevant
Copy link
Contributor Author

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

/cc @daschott @Keith-Mange @kumarvin123

@dcantah dcantah merged commit 2d5a2c3 into microsoft:master May 5, 2021
dcantah added a commit to dcantah/kubernetes that referenced this pull request Sep 22, 2021
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>
ibabou pushed a commit to ibabou/kubernetes that referenced this pull request Sep 28, 2021
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>
princepereira pushed a commit to princepereira/hcsshim that referenced this pull request Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants