Windows CI

[BenTheElder]

We should add CI for kind-on-windows.

AFAICT so far we cannot get github actions to create linux containers on windows, but we could probably bring up a GCE windows VM in a boskos managed project and run tests there?

Prow does not have windows nodes, but even if it did a windows container would not work, we need a windows VM or baremetal.

It would be nice to do this in a periodic job so we can check for breakage in a less manual way.

[BenTheElder]

NOTE: it is probably non-trivial to navigate kubernetes's CI to make this work. While we're looking for help, don't expect this to necessarily be an easy starter task!

We're looking for a full test of creating a cluster. We already verify cross compliation.

[wolf99]

Apologies if this is a naive suggestion; but could this help?

https://github.com/marketplace/actions/setup-wsl

[BenTheElder]

I think the issue is folks are primarily on WSL2 not WSLv1 (e.g. the only docs contributed so far are for WSL2 https://kind.sigs.k8s.io/docs/user/using-wsl2/), which requires virtualization support. Per setup-wsl:

WSLv2 is not explicitly supported, because as of this writing neither the Windows version running on GitHub hosted runners supports WSLv2, nor is Hyper-V enabled which is also necessary to enable WSLv2.

This is the problem we ran into trying to setup CI ourselves previously. @amwat and I hacked on this previously but hit that limitation with no nested virtualization support in the github actions environment.

We learned that macOS runners (and only macOS) on github.com do have virtualization support, but didn't manage to get docker desktop running. Later someone contributed vagrant/linux rootless configurations running under macOS for testing rootless. We might be able to run windows in a VM under macOS 😂 but I'm not sure about say, licensing ...

"self hosted" runners using cloud VMs from SIG K8s Infra might? be an option, but perhaps higher effort and more to maintain.