azure: put masters and workers into AvailabilitySets and ScaleSets

[philips]

ScaleSets currently cannot attach different disks to different virtual machines. This means that Kubernetes persistent volumes will not work with our setup for multi-machine.

To fix this we need to offer the ability to spin-up via AvailabilitySets instead. Should we create a separate module if someone wants to use AvailabilitySets vs ScaleSets similar to how you do with AWS?

cc @alexsomesan

[alexsomesan]

I wasn't aware of that limitation. Seems like we need to address this. I'll give availablity sets a try tomorrow.

…

On Wed, 22 Mar 2017 at 00:40, Brandon Philips ***@***.***> wrote: ScaleSets currently cannot attach different disks to different virtual machines. This means that Kubernetes persistent volumes will not work with our setup for multi-machine. To fix this we need to offer the ability to spin-up via AvailabilitySets instead. Should we create a separate module if someone wants to use AvailabilitySets vs ScaleSets similar to how you do with AWS? cc @alexsomesan <https://github.com/alexsomesan> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#93>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABC-mwl6-6AFjqU2wFJ-Mc0lU_Sq-RSQks5roF_UgaJpZM4MkjB6> .

[philips]

@alexsomesan thank you. Yes, I was unaware as well. Something we just learned about the product.

[alekssaul]

Also mentioned in : #168

[s-urbaniak]

upstream limitation of cloud-provider integration: kubernetes/kubernetes#40913

[discordianfish]

So I'm trying this right now, but not sure that the cloud-provider integration even works with availability sets. Let's see.