In `test/e2e/network`, there are currently 45 tests marked `[LinuxOnly]`, of which it seems that 37 are incorrect or at least dubious:
- 15 claim that Windows does not support `SessionAffinity`, which [was implemented in `pkg/proxy/winkernel` 4 years ago](https://github.com/kubernetes/kubernetes/pull/91701)
- 14 test dual-stack, which works on Windows but [is (was?) not fully supported by our CI environment](https://github.com/kubernetes/kubernetes/issues/100870)
- 3 need UDP support in agnhost, which the tests in question claim does not work, though I suspect this actually means "at [the time these tests were merged](https://github.com/kubernetes/kubernetes/pull/98636), the windows agnhost image had not been rebuilt with the [recently-added udp client](https://github.com/kubernetes/kubernetes/pull/98639) yet".
- 2 use `hostNetwork` pods, which [now exist in alpha on Windows](https://github.com/kubernetes/enhancements/issues/3503), so we ought to at least optionally be running them there
- 1 uses pod hostPorts, which have been [supported on Windows since 2020](https://github.com/containernetworking/plugins/pull/475).
- 1 is skipped because "IPv6 is not supported on Windows", which is not true

The seemingly-correct ones:
- 5 use SCTP, which AIUI the Windows kernel does not implement and does not plan to implement.
- 3 test partial DNS names (`kubernetes.default.svc`) which apparently are not supported by the Windows resolver

cc @claudiubelu @knabben @MikeZappa87
/sig windows
/sig network
[LinuxOnly] is egregiously misused at least in sig-network tests
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : [LinuxOnly] is egregiously misused at least in sig-network tests
Issue date:

--- start body ---
In `test/e2e/network`, there are currently 45 tests marked `[LinuxOnly]`, of which it seems that 37 are incorrect or at least dubious:
- 15 claim that Windows does not support `SessionAffinity`, which [was implemented in `pkg/proxy/winkernel` 4 years ago](https://github.com/kubernetes/kubernetes/pull/91701)
- 14 test dual-stack, which works on Windows but [is (was?) not fully supported by our CI environment](https://github.com/kubernetes/kubernetes/issues/100870)
- 3 need UDP support in agnhost, which the tests in question claim does not work, though I suspect this actually means "at [the time these tests were merged](https://github.com/kubernetes/kubernetes/pull/98636), the windows agnhost image had not been rebuilt with the [recently-added udp client](https://github.com/kubernetes/kubernetes/pull/98639) yet".
- 2 use `hostNetwork` pods, which [now exist in alpha on Windows](https://github.com/kubernetes/enhancements/issues/3503), so we ought to at least optionally be running them there
- 1 uses pod hostPorts, which have been [supported on Windows since 2020](https://github.com/containernetworking/plugins/pull/475).
- 1 is skipped because "IPv6 is not supported on Windows", which is not true

The seemingly-correct ones:
- 5 use SCTP, which AIUI the Windows kernel does not implement and does not plan to implement.
- 3 test partial DNS names (`kubernetes.default.svc`) which apparently are not supported by the Windows resolver

cc @claudiubelu @knabben @MikeZappa87
/sig windows
/sig network
--- end body ---
