Closed josephrodriguez closed 4 weeks ago
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.
Hi @javsalgar ,
Sure, I'll prepare a pull request for this feature request and let know here.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
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.