KAFKA-6416: Helm chart for deploying Kafka to Kubernetes #19249
+1,510
−1
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
github-actions
bot
added
triage
|
Thanks for the PR. Adding Helm charts to the project is a significant change and would require a KIP. You can find the KIP process in the wiki: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals |
mimaison
added
kip
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.
This PR adds a Helm chart for deploying Kafka to Kubernetes.
It is designed to run brokers and controllers in separate pods.
All the configuration is templated from Helm values and stored in ConfigMaps. These are mounted in the running containers.
The new
k8s_launchscript is used to copy the config files into the right place, format the storage and start Kafka. Specific storage classes can be set in the Helm values and will depend on the Kubernetes distribution/Cloud provider being used. The brokers and controllers are run as stateful sets so each one get its own persistent storage. I'm not sure I have the initialization quite right as the KRaft version shows as 0, as per the docs at Provisioning Nodes. I may need some assistance with this.