This repository has been archived by the owner on Jul 7, 2020. It is now read-only.
Added option --load-balanced for running in GKE #591
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
…e outside the node network.
|
Can one of the admins verify this patch? |
--all should be -a (or --show-all)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In GKE (Google's managed Kubernetes environment), the master nodes are outside the node network. When adding the StorrageClass with a node IP address, they cannot connect to Heketi.
Running the service as NodePort and using external IP address of one of the nodes would work, but I preferred using a non-ephemeral load balanced address. Of course some authentication should be in place. I added a warning for that.
Future work: setup firewall rule to only allow connects from the master nodes.
This change is