[bitnami/kafka] add support for helm parameter maps for extraConfig

[rubenvw-ngdata]

Name and Version

bitnami/kafka 28.1.1

What is the problem this feature will solve?

With the migration to Kafka 3.5, an extraConfig parameter was added to the chart.
We regret that this is just a text value instead of a helm parameter map.
This choice blocks the overloading of a certain setting via additional values.yaml layers.
With the current implementation, you need to duplicate all extraConfig if you want to change a single parameter in it.

As an example, instead of this

extraConfig: |
  max.message.bytes = 1048576
  offsets.topic.replication.factor = 3
  default.replication.factor = 3
  delete.topic.enable = true
  auto.create.topics.enable = false

we would prefer to have

extraConfig:
  max.message.bytes: 1048576
  offsets.topic.replication.factor: 3
  default.replication.factor: 3
  delete.topic.enable: true
  auto.create.topics.enable: false

to allow overloading.

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

helm parameter maps to allow overloading the extraConfig.

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

[rubenvw-ngdata]

Hi @carrodher, I created a PR to add this. Let me know what you think.

[carrodher]

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!