bitnami / charts

Bitnami Helm Charts
https://bitnami.com
Other
8.6k stars 8.98k forks source link

[bitnami/kafka] Setup of sasl authentication to external zookeeper during Kraft-Migration #27581

Closed ph311o closed 1 day ago

ph311o commented 5 days ago

Name and Version

bitnami/kafka 29.3.4

What architecture are you using?

amd64

What steps will reproduce the bug?

In https://github.com/bitnami/charts/issues/22729 the problem was addressed for brokers: SASL authentication to external Zookeeper was put into wrong config file. I fixed it in PR https://github.com/bitnami/charts/pull/23550.

During testing migration to kraft mode I recognized that the controller needs also a VolumeMount to the kafka_jaas.conf file to be able to properly connect to Zookeeper.

Are you using any custom parameters or values?

No

What is the expected behavior?

Controller Statefulset needs:

            {{- if .Values.sasl.zookeeper.user }}
            - name: kafka-config
              mountPath: /opt/bitnami/kafka/config/kafka_jaas.conf
              subPath: kafka_jaas.conf
            {{- end }}

like in https://github.com/bitnami/charts/blob/main/bitnami/kafka/templates/broker/statefulset.yaml#L314-L318

What do you see instead?

Controller is not able to finalize migration to kraft mode as it cannot connect to Zookeeper with proper SASL authentication.

Additional information

I will submit a PR to fix the issue.

carrodher commented 2 days ago

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.

ph311o commented 2 days ago

@carrodher I created PR. Please verify.

carrodher commented 2 days ago

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!