Evaluate Regional volumes for the two ZK pods meant to migrate at zone outage #191
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
and everyone would have to customize it, and if all zk pods used this we'd be spanning only two zones, not all.
storage class name, but apply different definitions.
|
This PR is a good fit for the breaking 5.0 release as it introduces storage classes for I haven't found a way to use for example |
This was referenced Nov 28, 2018
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 trying I'm not sure https://cloud.google.com/kubernetes-engine/docs/concepts/persistent-volumes#regional_persistent_disks was meant to be used with automatic volume provisioning. To me it appears to be useful only with single-pod statefulsets, due to the hard coded zone names.