-
-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provider not working since version 0.6 #383
Comments
@Aransh what Kafka version are you using? |
I'm actually using RedPanda (a Kafka-compatible broker), was probably relevant to mention 😅.
|
Hi @Aransh , I have the same problem. Can you please share your solution if you found something? |
@arkadiusjonczek no solution yet except using the old provider version. |
We're hitting the same issue with AWS Managed Kafka (MSK). Different versions of MSK. I'll ask my colleague to provided details. |
@Mongey After upgrading to 0.6.0 version Getting this error 12:57:20 Error: kafka: client has run out of available brokers to talk to: 3 errors occurred: TLS Brokers Note: Same code is working for 0.5.4 version |
@Mongey @errm Is this being worked on please? Also, as it was already suggested, documentation update would be great improvement. Thank you. |
Same issue here. |
Hi Team, Any update? |
@EliranTurgeman / @srikanth520 / @yermulnik / @Aransh Can you please provide examples of your configuration, along with details of the Kafka service, and versions you're using. |
@Mongey Please see #383 (comment) — @srikanth520 and I are on the same team. |
@yermulnik There is no terraform config provided. |
Ouch, I just double checked and couldn't reproduce the issue (currently we're at I'll talk to @srikanth520 to see whether I might be missing something from his setup. Will keep you posted. UPD: I re-read through the history of our internal ticket and it looks like the issue was with MSK cluster of |
@Mongey I can try and help with that. Relevant terraform files are pretty standard:
example topic:
And on apply, after approving the plan:
|
@Aransh I have just tried with red panda serverless and cannot reproduce. |
@Mongey Hmmm... that's odd, we've had this issue reproduced by 3 of our teams in several different redpanda deployments... |
I'm having the same issue with my self-hosted redpanda broker. In the redpanda logs I see the following error: kafka - connection_context.cc:362 - Error while processing request from 10.244.0.84:55402 - Unsupported version 9 for metadata API. Maybe that is related? |
Maybe try setting |
Already tried that, no dice... |
|
Been using this provider for a while now, since version 0.6 was released I am unable to use it..
I am getting this error when trying to manage "kafka_topic" resources:
Reverting the version 0.5.4 (with no other configuration changes) works right away.
Any directions would be greatly appreciated
The text was updated successfully, but these errors were encountered: