Closed vipul-06 closed 5 months ago
Hello can anyone update me on this? This is required on urgent basis
Hi @vipul-06,
I'm sorry but we can not give support for a chart version that was released more than two years ago. Even if we found a bug in that specific version, it is possible that the issue was already fixed and it is not possible to release new patches for older majors.
Are you able to reproduce the issue using the latest version of the chart?
Since you would be upgrading several majors, I would recommend checking the Upgrading notes in addition to both upstream Zookeeper and Kafka breaking changes.
Hi @migruiz4 can you just tell me that in this chart version 19.1.3 I am able to connect to external cloud service through this configuration. But my internal connection is also getting stopped. I want to keep my all internal connection as plaintext only.
Yes, it should be possible. The kafka chart was configured with 3 listeners INTERNAL
using port 9093 for inter-broker communications, CLIENT
using port 9092 for internal client connections and EXTERNAL
using port 9094 for external client connections.
# Enables 'EXTERNAL' listener
externalAccess:
enabled=true
# Security protocols for each listener
auth:
# CLIENT
clientProtocol: plaintext
# EXTERNAL CLIENTS
externalClientProtocol: sasl_tls
# INTERNAL (inter-broker)
interBrokerProtocol: plaintext
You can find the README for version 19.1.3 here, including examples for external access configuration.
If I set as above mentioned b you I get the zookeeper error earlier mentioned. If I set like this :
auth: clientProtocol: sasl_tls externalClientProtocol: sasl_tls interBrokerProtocol: plaintext
Then my external connection is successful but my internal connection also required sasl_tls. This is same issue as mine:
https://stackoverflow.com/questions/74046781/passing-jaas-config-to-bitnami-kafka-helm-chart-for-sasl-plain
As previously mentioned, there is no point for us to troubleshoot issues with older versions of the chart, because the issue may have already been fixed and even if we found the root cause of the issue there is no point because we can not release patches for older versions.
I'm sorry but you may need to try using the latest version of the chart or I may not be able to further help you.
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 19.1.3
What architecture are you using?
None
What steps will reproduce the bug?
I am trying to setup externalClientProtocol as sasl_tls in bitnami kafka running in GKE cluster. I already have changed some paramters. Attached my ssl certificate as a secret. But I am facing issues.
Are you using any custom parameters or values?
What is the expected behavior?
No response
What do you see instead?
Error I am facing is :