cloud controller manager broken for Windows

[jackfrancis]

Seems to be easily reproducible:

1. Enable cloud controller manager in your api model, e.g.:

...
      "orchestratorProfile": {
          "orchestratorType": "Kubernetes",
          "kubernetesConfig": {
              "useCloudControllerManager": true
          }
      }
...

Include a Windows node pool. Nodes are provisioned, but never seem to join the cluster.

[jackfrancis]

Relevant test config showing this failure:

https://github.com/Azure/aks-engine/blob/master/test/e2e/test_cluster_configs/cloud_controller_manager.json

[marosset]

@chewong do you know if CCM + Windows was ever testing in aks-engine?

[chewong]

Yea the test was included in #3044

[chewong]

https://github.com/Azure/aks-engine/blob/master/parts/k8s/windowscsiproxyfunc.ps1#L14-L15 isn't able to extract csi-proxy binary from https://kubernetesartifacts.azureedge.net/csi-proxy/v0.1.0/binaries/csi-proxy.tar.gz since the file structure has changed, which causes windows kubelet not be able to start properly. I will trigger a Jenkins run to validate the change once it's fixed.

[jackfrancis]

Thanks for hunting down, @chewong!

[chewong]

The CSI proxy download link has been fixed, verified by https://upstream.jenkins.azure-containers.io/blue/organizations/jenkins/k8s-create-cluster-matrix/detail/k8s-create-cluster-matrix/229/pipeline.