Keda-operator cannot create KafkaScaledObject due to Kafka client error "client has run out of available brokers to talk to (Is your cluster reachable?)" #1764
-
Hi experts, My other consumer pods are able to successfully publish and consume messages with the Kafka cluster brokers. Not sure how to debug this? Only notable difference in my cluster is that Kafka brokers are on 9094 instead of port 9092. Not sure if this the reason why it's failing. Any help is appreciated. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Could you please share your |
Beta Was this translation helpful? Give feedback.
-
Hello, Thanks |
Beta Was this translation helpful? Give feedback.
-
Hello, I coded a feature to be able to specify your kafka version. |
Beta Was this translation helpful? Give feedback.
Hello,
After lot of troubleshooting, found that the config version property in the sarama client needs to be 0.10.2.0 and only then the client is able to talk to the brokers. I was able to build a sample go app with the same version of sarama client. I just tweaked the version and it was able to connect to kafka brokers (v.0.8) . Is there a way in keda to pass this value as a environment variable?
Thanks