Can't use calico on windows on EKS due to forced network mode

[davidgiga1993]

We're running a EKS cluster but are not using the amazon vpc cni, but rather plain calico vxlan which works great.

However when using windows nodes the operator forces the daemonset KUBE_NETWORK to *.vpc as it uses the auto-detected k8s provider rather than the cni.type configuration that is also used for the linux installation

On linux this works as it uses the cni.type config parameter

Expected Behavior

The windows installation should also follow the cni.type configuration

Current Behavior

The kubernetes network on windows gets forced to the default CNI for the auto-detected k8s provider

Possible Solution

Change the parameter to evaluate the cni.type config instead.
We build a custom fork which implemented this change and it worked fine in our environment.

Steps to Reproduce (for bugs)

1. Install on EKS using the following config:

spec:
  variant: "Calico"
  kubernetesProvider: EKS
  cni:
    type: Calico

3. Run a windows node
4. The KUBERNETES_NETWORK is set to vpc.* rather than calico.*

[tmjd]

@coutinhop you added the windows support so I think this is something you should take a look at.