WIP three node cluster without PetSet #9
Closed
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
…hich we don't use yet
…eta, because that blocks use of the services
…caling, so do #4 now
…he hostnames (broker-0-xxxxx) as DNS name
…ffect signal handling.
solsson
force-pushed
the
nopetset-kafka
branch
from
7df41e2 to
1f7f53d
Compare
Closed
…ocker-kafka-persistent in master
…ly to avoid issues with persistent volumes not being available to the new pod at restarts or node upgrades
|
As expected, we only needed this until we upgraded to k8s 1.5. See #14. |
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.
Due to GKE de-supporting PetSet in our zone, we're back to fixed size clusters using per-pod resource definitions.
Hopefully k8s 1.5 will get PetSet into beta (kubernetes/kubernetes#18016 (comment), kubernetes/kubernetes#28718) and we'll never need to merge this branch. I therefore avoided all kinds of scripting.
Some improvements from this branch could probably be cherry picked. In particular there's an official zookeeper image now and the branch uses that one instead of init container + 3.5.2-alpha. On the other hand dynamic reconfiguration added in 3.5 may be crucial for proper PetSet initialization. Official image has no 3.5 tag yet but I experimented with it in https://github.com/solsson/zookeeper-docker/tree/3.5 31z4/zookeeper-docker#5.