Windows image configuration scripts and Azure builder

[jsturtevant]

Initial support for configuring Windows nodes for CAPI. This is the first step for Windows support as described in Windows Proposal in CAPI: kubernetes-sigs/cluster-api#3616 and partly solves #30.

The current scripts work to create an image but I am still testing that the image works with a provider like CAPZ. I wanted to open the PR to get feedback on the setup. Update: now tested via CAPZ #382 (comment)

A few notes:

• Kubeadm support for Windows is currently uses https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/kubeadm/scripts/PrepareNode.ps1. I referred to that script for some of the set up.
• Most windows users are use to scripts for configuration over ansible. I initially started this with scripts but the customization required in the scripts and use with Packer was quickly making it unmaintainable. The final ansible solutions feels much cleaner to me and closer to the Linux configuration which makes it easier to grok.
• The Ansible and packer configuration has been split out since there is not enough in common. I think having them in separate folder will make the maintenance easier longer. Initially tried to keep the packer configuration re-use high but ended splitting it out into it's own folder under config/windows to keep it cleaner since there were so many different setting between Windows/linux.
• The ansible files for windows are in an awkward spot, It would look cleaner if there was a clear split between Linux and Windows under the ansible folder. Didn't include that change here to minimize the diff.

Looking forward to feedback.

[CecileRobertMichon]

CI is failing with �[0;32m vhd-windows-2019: fatal: [default]: FAILED! => {"msg": "winrm or requests is not installed: No module named 'winrm'"}�[0m

[jsturtevant]

This is ready for final review. I have tested it against a branch on CAPZ and have Windows machines and pods working:

kubectl get pods -A     
NAMESPACE     NAME                                                 READY   STATUS    RESTARTS   AGE
default   iis-1809-668c5b9c87-zxklh                            1/1     Running   0          105m

kubectl get nodes -o wide                          
NAME                         STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION     CONTAINER-RUNTIME
test-5-control-plane-6crm6   Ready    master   39h   v1.19.1   10.0.0.6      <none>        Ubuntu 18.04.5 LTS               5.4.0-1025-azure   containerd://1.3.4
test-5-control-plane-fjw76   Ready    master   39h   v1.19.1   10.0.0.5      <none>        Ubuntu 18.04.5 LTS               5.4.0-1025-azure   containerd://1.3.4
test-5-control-plane-hn8rb   Ready    master   39h   v1.19.1   10.0.0.4      <none>        Ubuntu 18.04.5 LTS               5.4.0-1025-azure   containerd://1.3.4
test-5-md-0-cpj5q            Ready    <none>   39h   v1.19.1   10.1.0.7      <none>        Ubuntu 18.04.5 LTS               5.4.0-1025-azure   containerd://1.3.4
test-5-md-0-vsbmx            Ready    <none>   39h   v1.19.1   10.1.0.5      <none>        Ubuntu 18.04.5 LTS               5.4.0-1025-azure   containerd://1.3.4
test-5-w-757gp               Ready    <none>   39h   v1.19.1   10.1.0.4      <none>        Windows Server 2019 Datacenter   10.0.17763.1397    docker://19.3.12
test-5-w-p8vbj               Ready    <none>   39h   v1.19.1   10.1.0.6      <none>        Windows Server 2019 Datacenter   10.0.17763.1397    docker://19.3.12

This does not include support for running goss. When I tried it out I found native windows support didn't work and opened a PR that will enable it. Once that merges and a new release is cut I can follow up with support.

I also have an open question on the location of the Windows ansible scripts. It currently feels like an awkward spot mixed in with the Linux files. Any one have thoughts on if that is ok or files should be re-arranged?

[marosset]

The changes LGTM

[jsturtevant]

Yes this is ready. I just did a re-base to clean up the commits to a reasonable set and tested an image with kubernetes-sigs/cluster-api-provider-azure#1036

[jsturtevant]

/test pull-azure-sigs

[perithompson]

Changes LGTM as well @jsturtevant @CecileRobertMichon

[CecileRobertMichon]

/lgtm

will leave it open until tomorrow EOD unless there are any objections

[codenrhoden]

No objections here.
/lgtm

[jsturtevant]

/test pull-azure-sigs

[jsturtevant]

/test pull-azure-sigs

[CecileRobertMichon]

/lgtm
/approve

great work @jsturtevant 🎉

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon, jsturtevant, ksubrmnn

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [CecileRobertMichon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment