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.

Sign up for GitHub

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

Jump to bottom

[bitnami/kafka] add topologyKey #32791

Open
simonostendorf opened this issue Apr 3, 2025 · 3 comments · May be fixed by #32792
Open

[bitnami/kafka] add topologyKey #32791

simonostendorf opened this issue Apr 3, 2025 · 3 comments · May be fixed by #32792
Assignees
@carrodher
Labels
feature-request kafka triage Triage is needed

Comments

@simonostendorf
Copy link

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
@github-actions github-actions bot added the triage Triage is needed label Apr 3, 2025
@simonostendorf simonostendorf linked a pull request Apr 3, 2025 that will close this issue
Open
4 tasks
@javsalgar javsalgar added the kafka label Apr 7, 2025
@javsalgar
Copy link
Contributor

Hi,

Would the section affinity work for your use case? That would allow you to set the any affinity settings to the workloads.

@javsalgar
Copy link
Contributor

BTW, I saw that you created a PR. Thank you so much!

@simonostendorf
Copy link
Author

Hi,

Would the section affinity work for your use case? That would allow you to set the any affinity settings to the workloads.

@javsalgar I thought that adding the topologyKey value would be better because all other bitnami charts handle it that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carrodher carrodher

Labels
feature-request kafka triage Triage is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[bitnami/kafka] add topologyKey value simonostendorf/bitnami-charts
3 participants
@javsalgar @carrodher @simonostendorf