lhotari commented on issue #601: URL: https://github.com/apache/pulsar-helm-chart/issues/601#issuecomment-2804594024
@trynocoding Unfortunately the pulsar-helm-chart issues aren't suitable for support questions since there's hardly any audience. Your question more or less duplicates #423 which is also a question in the pulsar-helm-chart issue tracker, without a solution. The correct place for questions is https://github.com/apache/pulsar/discussions/categories/q-a . > I'd like to ask if it's possible to access the broker from outside the cluster without enabling pulsar-proxy. Thank you for your help in advance. It is possible, but there's no proof-of-concept in any documentation. It will most likely require changes to Apache Pulsar Helm chart as well. One part missing from your configuration is the use of `bindAddresses` configuration. https://github.com/apache/pulsar/blob/066a20c33fe28ed0bb5ec9b3846ed67560877302/conf/broker.conf#L68-L69 Each advertised listener should have a unique `bindAddress` & `port` in `bindAddresses` so that the solution could work. let's say something like ``` bindAddresses=internal:pulsar://0.0.0.0:6650,external:pulsar://0.0.0.0:16650 ``` The node port would have to map to port 16650 in the above example. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
