Lari Hotari

When configuring the nodeport, you'd have to ensure that each broker pod can be individually and uniquely addressed. That might be the problem in your configuration. The current Helm chart...

it would also be useful to have a separate nodeport service that has all available brokers in it. that's what should be used for the service url in clients. in...

> [@lhotari](https://github.com/lhotari) Thank you, following above method, I can now access it outside the cluster @trynocoding would you be interested in contributing the changes to pulsar-helm-chart or sharing how you...

> At first, I only exposed the Pulsar protocol externally, which allowed normal access，the configuration is as follows @trynocoding Just curious, did you modify the Helm chart to configure the...

> I deployed the cluster using pulsar-operator (currently under development) and did not use the helm chart @trynocoding Ok, I see. Is it going to be opensource or is it...

> As follows, outside the cluster，the broker still returns the internal access address. I would expect the broker to return an externally accessible address for the pulsar protocol, not an...

One of the gaps: https://github.com/apache/pulsar/pull/22062

docs have been updated some time ago: https://pulsar.apache.org/docs/4.0.x/concepts-multiple-advertised-listeners

> You can also use an NLB if I am not mistaken. We are about to start using it using an NLB exposed internally so that other services can reach...

> Instead of setting the parameters of option, set the parameters of childOption. Otherwise it will not take effect @keyboardbobo Yes that's correct. Have you run across a problem that...