Update k8s platform master bootstrap #89
Merged
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
robertodauria
approved these changes
Dec 13, 2018
There was a problem hiding this comment.
Reviewed 3 of 3 files at r1.
Reviewable status: 0 of 1 LGTMs obtained
robertodauria
approved these changes
Dec 13, 2018
complete! 1 of 1 LGTMs obtained
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.
After discovering that internal loadbalancers only work within a single region, we must create the k8s masters in the same region that AppEngine is pinned to (for the epoxy boot-api server).
In practice this means that k8s must run in us-east1 for mlab-sandbox & mlab-oti and can remain in us-central1 or mlab-staging.
If we move epoxy out of app engine or adopt an alternative to internal loadbalancers for access to the token servers, then we can revisit this decision.
This change is