Research and document what efforts are required to integrate Windows builds into the following repositories:

https://github.com/rancher/image-build-calico
https://github.com/rancher/image-build-cni-plugins
https://github.com/rancher/image-build-flannel
https://github.com/rancher/image-build-base
https://github.com/rancher/image-build-kubernetes

Our eventual goal will be multiple spikes to demo:

rancher/image-build-base:

• compiling goboring for Windows in image-build-base to be consumed downstream by all image-build-* repos that use the base image (including RKE2)
• switch image-build-base to use SLES instead of golang alpine to match rancher/rancher

Calico:

• compiling calico binaries for Windows (which moves us away from pulling in upstream and aligns us with the linux dev/build/release cycle for rke2 calico) using the existing Dockerfile and Makefile
• using goboring for Windows to compile Calico binaries

Flannel:

• using goboring for Windows to compile the Flannel binary (which moves us away from pulling in upstream and aligns us with the linux dev/build/release cycle for rke2 flannel)

Goboring Compiled Kubernetes Components for Windows:

• consume image-build-base containing goboring for windows to compile kubelet, kube-proxy, and kubectl

CNI Plugins for Windows:

• compiling CNI plugin binaries for Windows in rancher/image-build-cni-plugins instead of pulling in the upstream tar.gz
• compiling the flannel-io/cni-plugin binary for Windows in rancher/image-build-cni-plugins (which moves us away from pulling in upstream and aligns us with the linux dev/build/release cycle for rke2 flannel)

Linked Issues:
#103