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

[bitnami/kafka] Enable configuration for StatefulSet revisionHistoryLimit #29569

Open
josephrodriguez opened this issue Sep 23, 2024 · 2 comments
Assignees
Labels

Comments

@josephrodriguez
Copy link

Name and Version

bitnami/kafka 30.1.4

What is the problem this feature will solve?

For all StatefulSet in the chart there is not way to configure the revisionHistoryLimit specification property.

What is the feature you are proposing to solve the problem?

Include a revisionHistoryLimit parameter in values.yaml with a default value that can be redefined on chart value override. This value is going to be use to set the property on the specific StatefulSet for controllers and brokers

What alternatives have you considered?

Actually the workaround it's a combination with Kustomization creating patches operations to set the value for all StatefulSet , kafka-brokers and kafka-controllers.

@github-actions github-actions bot added the triage Triage is needed label Sep 23, 2024
@javsalgar javsalgar changed the title Enable configuration for StatefulSet revisionHistoryLimit [bitnami/kafka] Enable configuration for StatefulSet revisionHistoryLimit Sep 24, 2024
@javsalgar
Copy link
Contributor

Hi!

Thank you so much for the feature request! I will forward it to the team but as it is not a critical feature we cannot guarantee an ETA. If you want to speed up the process, you can submit a PR adding the value and the team will check it.

@josephrodriguez
Copy link
Author

Hi @javsalgar ,

Sure, I'll prepare a pull request for this feature request and let know here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants