Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Switch from a Zonal Managed Instance Group to a Regional Managed Instance Group #26

Merged
merged 4 commits into from
Sep 11, 2018

Conversation

josh-padnick
Copy link
Collaborator

@josh-padnick josh-padnick commented Sep 11, 2018

This PR switches from a Zonal Managed Instance Group to a Regional Managed Instance Group. This way, Consul nodes launch in a diversity of physical data centers ("Zones") within a given region instead of all in a single data center (Zone).

This PR also:

  • Fixes an issue where users could not specify the root disk type and size for "private" clusters.
  • Updates to the latest version of Consul (v1.2.2)
  • Enables access to the cluster via 0.0.0.0/0 by default (along with a hearty warning)

'cc @infosecgithub @bgt101

Previously all instances were deployed into a single Zone. Now they're deployed across multiple Zones within a single Region!
Also, set Consul client and server nodes to be accessible by 0.0.0.0/0 in root example by default.
@josh-padnick
Copy link
Collaborator Author

Manual tests are passing, so I'm going to merge. The next update to this repo will be automatically running automated tests in CircleCI on every commit.

@josh-padnick josh-padnick merged commit 3f0cd57 into master Sep 11, 2018
@josh-padnick josh-padnick deleted the multizonal branch September 11, 2018 23:41
@josh-padnick josh-padnick changed the title Switch from a single-zone Managed Instance Group to a Multi-Zonal Group Switch from a Zonal Managed Instance Group to a Regional Managed Instance Group Sep 12, 2018
@josh-padnick josh-padnick mentioned this pull request Sep 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants