WIP Kubernetes init-container image to set per-pod config #8
Conversation
This file contains hidden or 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
as even without additional jars it needs properties files.
No longer start any service by default
|
I ended up doing this with a bash script in a ConfigMap, running on the same kafka image as kafka. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
For trivial stuff like broker-id, and non-trivial stuff looked up from the Kubernetes API, like Yolean/kubernetes-kafka#41.
Started out as a Go learning project. The branch
bazel-buildhas an attempt to build that does not suffer from thego getalways HEAD policy.#5 will have to be merged to master first