Support for windows worker nodes

[awesomenix]

/kind feature

Since kubernetes 1.14 just GA windows worker nodes, add support for the same in cluster api

Describe the solution you'd like

1. VM Extension service needs to be refactored to handle CSE in Microsoft.Compute namespace

   cluster-api-provider-azure/pkg/cloud/azure/services/virtualmachineextensions/virtualmachineextensions.go

   Line 69 in f53efdb

   Type: to.StringPtr("CustomScript"),

2. Change default CNI to use Flannel, which has windows support (part of addons)
3. Change VM Startup scripts to include support for windows, following guide here https://github.com/Azure/aks-engine/blob/1242dcc6fa5f7a55c685eb94fd82d8f668e90965/parts/k8s/kuberneteswindowssetup.ps1

Anything else you would like to add:
aks-engine has successful implementation, following the process would help implementing it here.

Environment:

• cluster-api-provider-azure version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[justaugustus]

Currently blocked on adding support for Kubernetes 1.14: #154
I'm fine with this, but the CNI needs to be configurable. Default to weave for most cases, but use flannel, if you need to support Windows.

/priority important-longterm
/milestone next

[justaugustus]

Added Canal (flannel + Calico policy) as CNI in #181.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[justaugustus]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@justaugustus: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[justaugustus]

Issue needs to updated to outline proposal for Windows support prior to implementation.
cc. @PatrickLang @marosset @ksubrmnn
/assign @marosset @CecileRobertMichon

[k8s-ci-robot]

@justaugustus: GitHub didn't allow me to assign the following users: marosset.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

Issue needs to updated to outline proposal for Windows support prior to implementation.
cc. @PatrickLang @marosset @ksubrmnn
/assign @marosset @CecileRobertMichon

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[justaugustus]

/assign @ksubrmnn
/unassign @CecileRobertMichon

[k8s-ci-robot]

@justaugustus: GitHub didn't allow me to assign the following users: ksubrmnn.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @ksubrmnn
/unassign @CecileRobertMichon

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[justaugustus]

/assign @ksubrmnn

[timothysc]

@CecileRobertMichon - Is this targeted for any near-term milestone? If we can lend a hand here just let us know, I think it would be great to enable windows deployments.

cc @nader-ziada @yastij @ncdc

[ksubrmnn]

cc @JocelynBerrendonner

[k8s-ci-robot]

@ksubrmnn: GitHub didn't allow me to assign the following users: JocelynBerrendonner.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/unassign @ksubrmnn
/assign @JocelynBerrendonner

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ksubrmnn]

/assign @ksubrmnn @marosset

[CecileRobertMichon]

Windows CAEP doc authored by @jsturtevant and @ksubrmnn is under review

[jsturtevant]

/assign

[jsturtevant]

The image support for Windows is in progress: kubernetes-sigs/image-builder#382

[CecileRobertMichon]

/lifecycle active