Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use init container for per-pod config #47

Merged
merged 8 commits into from
Jul 27, 2017
Merged

Conversation

solsson
Copy link
Contributor

@solsson solsson commented Jul 27, 2017

Next step after mounting config in #46. Idea raised in #41 (comment).

Now we can see where we find config most maintainable, and extendable:

  • Edit the .properties in the ConfigMap
  • Add --override
  • Patch .properties through init container

of not forwarding signals as Alpine did.
Kafka logs say nothing, and after 30s the container is terminated.
With /bin/bash instead the log indicates shutdown behavior.

This reverts commit c188f43.
modify config prior to kafka start. My aim with this is to
get rid of the /bin/sh startup scripts and use bin + args directly.
avoiding a layer of indirection and the associated gotchas with signals.
@solsson solsson merged commit 752cd45 into switch-to-debian-image Jul 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant