Skip to content
This repository has been archived by the owner on Feb 5, 2020. It is now read-only.

[WIP] Reimplement Azure Scale Sets #2429

Closed
wants to merge 4 commits into from

Conversation

justaugustus
Copy link
Contributor

@justaugustus justaugustus commented Nov 20, 2017

Background

Currently, Tectonic Installer does not support Azure Scale Sets as a result of a limitation in the Azure VMSS API. The VMSS API does not allow a consumer to access individual nodes in a Scale Sets, meaning integration points, like Kubernetes Cloud Provider and attaching disks to individual nodes (a la Persistent Disks) is not supported.

In an effort to provide the richest feature set to all Azure customers, we made the decision to remove the Scale Sets implementation from the Tectonic Installer.

Support for Azure Scale Sets has been recently called out as a requirement in several venues, and we will need to push on the upstream Kubernetes / Microsoft Azure community to drive this forward.

This PR is intended as a reference implementation of Tectonic Installer using Azure Scale Sets and is here for testing purposes and early review.
There are no guarantees as to its' functionality and should be considered buyer beware.

Upstream tracking PR:

Kubernetes related:

Tectonic related:

In the meantime, @alexsomesan / @s-urbaniak / @squat, would you mind taking a first pass?

cc: @robszumski / @metral / @sym3tri / @colemickens

@coreosbot
Copy link

Can one of the admins verify this patch?

@cpanato
Copy link
Contributor

cpanato commented Jan 2, 2018

@justaugustus can you please rebase and resolve the conflict? thanks!

1 similar comment
@cpanato
Copy link
Contributor

cpanato commented Jan 22, 2018

@justaugustus can you please rebase and resolve the conflict? thanks!

@justaugustus
Copy link
Contributor Author

@cpanato Thanks for following up on this! I'm going to take a look at updating the PR next week.

@justaugustus
Copy link
Contributor Author

Closing this as it's drifted from upstream and I'm thinking of implementing it slightly differently.
Stay tuned!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants