You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
I want to connect extension to kafka on Kubernetes.
I use vscode with remote-ssh extension to access to pc.
And I download kafka extension and try to connect to my kafka.
First I try to connect with kafka's cluster ip(10.99.116.43), but it failed.
In vscode-kafka, it shows Topics and brokers but couldn't see Topics' config.
Cause brokers' IP in extension is changed to dns name (kafka-service1.kafka.svc.cluster.local), I just add cluster ip to /etc/hosts.
Now I can see Topics' config but not Brokers' config.
I got error like
Unexpected broker id, expected 1 or empty string, but received ConfigResource(type=BROKER, name='3').name
Sorry, this is a known issue in https://github.com/SOHU-Co/kafka-node. I fixed it upstream (SOHU-Co/kafka-node#1280) but the change is still awaiting the original author publishing a new version of the library to npm. As soon as it is available I will provide an update to the extension.
I just published 0.8.0 which brings in latest kafka-node (5.0.0) that includes my upstream fix. Can you try make sure you are on the latest version (rolling out now) and verify that it fixes the issue for you?
Hi.
I want to connect extension to kafka on Kubernetes.
I use vscode with remote-ssh extension to access to pc.
And I download kafka extension and try to connect to my kafka.
First I try to connect with kafka's cluster ip(
10.99.116.43
), but it failed.In vscode-kafka, it shows Topics and brokers but couldn't see Topics' config.
Cause brokers' IP in extension is changed to dns name (
kafka-service1.kafka.svc.cluster.local
), I just add cluster ip to/etc/hosts
.Now I can see Topics' config but not Brokers' config.
I got error like
at all brokers.
here is some info about kubernetes kafka service.
This is env in kafka1
And when I click Broker 1 config
The text was updated successfully, but these errors were encountered: