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
We use a corporate proxy to hit the confluent kafka from the kubernetes hosted application. To amend the proxy in the kafkajs used application, socketFactory has been used as per this documentation - https://kafka.js.org/docs/configuration#custom-socket-factory.
I see the confluent kafka javascript support says that the socket factory is no longed supported. Is there any aleternative provided for amending the proxy details to make the kafka call go through for kafkajs migration or for the fresh usage?
Looking for an advise on this. Any help would be much appreciated, thanks!
The text was updated successfully, but these errors were encountered:
Hey - at the moment, this isn't supported. There are no plans in the near future to add a workaround for this. There are some suggestions here about how to work around similar issues but it requires changing some broker-side configurations.
We use a corporate proxy to hit the confluent kafka from the kubernetes hosted application. To amend the proxy in the kafkajs used application, socketFactory has been used as per this documentation - https://kafka.js.org/docs/configuration#custom-socket-factory.
I see the confluent kafka javascript support says that the socket factory is no longed supported. Is there any aleternative provided for amending the proxy details to make the kafka call go through for kafkajs migration or for the fresh usage?
Looking for an advise on this. Any help would be much appreciated, thanks!
The text was updated successfully, but these errors were encountered: