Place ASG instances across AZs #182
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey Sean. Sure.
Originally I kept only the etcd / master nodes in a single AZ (in general I think it is best to keep etcd node as close to each other as possible); and had the worker nodes spread over multiple AZs. Now, in preparation for moving to federation, I've pulled the worker nodes back into a single AZ to keep things together.
To answer your question I'm leaning toward using federation to provide HA. I'm finishing off a major update (ignition files) right now. After that I'll be working on a few new things, including federation.
… On May 24, 2017, at 1:37 PM, Sean Knox ***@***.***> wrote:
I just noticed this was an intentional decision: 56ae92c
@wellsie can you explain a bit more the reasoning behind moving all worker instances to a single fault domain?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
My understanding is federation is still a ways off before being a viable production option. It seems premature to remove proven HA options provided by AWS infrastructure today. To be fair, I haven't followed the federation SIGs closely for a bit. Where are they today? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ASG had been hardcoded to a single subnet/availability zone. This passes in all available private VPC subnets/AZs so worker instances will be spread across them (matching the documentation).