I think I found the answer to my question here: https://pulsar.apache.org/docs/en/2.5.1/deploy-bare-metal/#docsNav
(a) No need to use the proxy (b) Yes, we can use a single DNS entry covering all brokers (c) If using a single DNS entry, no need to reconfigure the clients sounds right? On Fri, Jan 14, 2022 at 11:51 AM Tecno Brain <[email protected]> wrote: > Hello, > > I have a Pulsar cluster (3 bookies, 3 brokers, 2 proxies) running in > Kubernetes. > My clients applications are also in Kubernetes. My client applications are > currently configured to use the proxy. > > > The proxies are load balanced on > > pulsar-proxy.example.com > > Each proxy is configured with a single entry on > > brokerServiceURL=pulsar://brokers.example.com:6650 > > brokers.example.com is load balancing the 3 brokers. > > I have some questions that I have not been able to get an answer to by > reading the docs. > > a) Since all my client applications are in the same Kubernetes space, do I > really need to use the proxy? Seems to me that the proxy is only needed if > my clients could not connect to the brokers directly and that the proxy is > adding some overhead. > > b) If we do not use the proxy, can we configure the client with the > single load-balanced broker address? Or do we need to provide a list of > individual brokers to the client? Will the client get the list of all > brokers and connect directly to them? > > c) If I provide a list of individual brokers (broker1, broker2, broker3) > to my client, but later I add more brokers (or remove some), I would need > to eventually reconfigure my client application with the list of active > members, right? > > Thanks a lot > > -Jorge > > > >
