-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Closed
Labels
Description
Name and Version
bitnami/kafka 32.1.3
What is the problem this feature will solve?
Currently the kafka chart doesnt allow to specify the topologyKey für the pod anti affinity so kubernetes.io/hostname is always used.
I want to use topology.kubernetes.io/zone as topologyKey to spread the kafka controllers between 3 availability zones.
What is the feature you are proposing to solve the problem?
I would suggest to add the topologyKey value to the values.yaml of the kafka chart and parse it to the pod anti affinity.
I am not sure where I should put the values (because we have controllers and brokers in this chart) and if there are other things to concider. I could try to open a PR and we can discuss these things in the PR review.
What alternatives have you considered?
No response