Closed ghost closed 1 year ago
Hi,
There is currently a major refactor of the kafka chart that should most of the issues:
Could this issue just be caused by the fact that kraft is enabled by default since 22.0.0? In any case you will need to set kraft.enabled=false
and enable zookeeper to proceed, even after the refactoring I believe.
Hi there!
We have released a new major of the bitnami/kafka chart (24.x.x) which refactors the chart architecture and configuration.
Could you please confirm if this issue persists in the latest version?
You can find all the changes introduced in this version as well as some guidance on how to upgrade in the Upgrading notes
Thanks, will give it a try.
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.
Could this issue just be caused by the fact that kraft is enabled by default since 22.0.0? In any case you will need to set
kraft.enabled=false
and enable zookeeper to proceed, even after the refactoring I believe.
@MisterTimn How do I do this? The 'values.yml' (see above) I'm currently using is from an example I'm following, and I don't see any setting related to Kraft or zookeeper.
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
kafka-23.0.5 3.5.0
What architecture are you using?
amd64
What steps will reproduce the bug?
Docker version
KinD version
Helm version
Deploy mongodb service and client. Create a database and user.
Build kafka-connect image and push to DockerHub (see below for Dockerfile used)
Deploy kafka and kafka-connect (see below for values.yml)
Reference:
Are you using any custom parameters or values?
kafka-connect Dockerfile
values.yml
What is the expected behavior?
Expected to see a mongodb pod, a kafka pod, a kafka-connect pod and a zookeeper pod running.
What do you see instead?
There's no zookeeper, and the kafka and kafka-connect pods fail:
Additional information
Following this article: https://tanzu.vmware.com/developer/guides/kafka-mongodb/ and trying to reproduce what's in there.