Kafka clients need to be able to differentiate the different brokers, and have explicit control which broker to connect to.
Why? Each partition resides in a specific broker, and the client needs to connect to the partition leader to perform read & writes, if they are all under the same virtual ip, clients won't be able to connect to a specific controller at their own will and will break down. However, you could put brokers behind a VIP for bootstrapping. but you still need to give them individual ip/hostname(preferred) so clients can connect directly. If you definitely prefer VIP, create one VIP for each broker. [image: Confluent] <https://www.confluent.io> Wu Shilin Solution Architect +6581007012 Follow us: [image: Blog] <https://www.confluent.io/blog?utm_source=footer&utm_medium=email&utm_campaign=ch.email-signature_type.community_content.blog>[image: Twitter] <https://twitter.com/ConfluentInc>[image: LinkedIn] <https://www.linkedin.com/company/confluent/>[image: Slack] <https://slackpass.io/confluentcommunity>[image: YouTube] <https://youtube.com/confluent> [image: Kafka Summit] <https://www.kafka-summit.org/> On Mon, Jul 5, 2021 at 12:04 AM sunil chaudhari <sunilmchaudhar...@gmail.com> wrote: > Honestly I didnt get this question. > Please elaborate. > > > On Sun, 4 Jul 2021 at 5:34 PM, M. Manna <manme...@gmail.com> wrote: > > > Hello, > > > > Is it currently possible to use a single endpoint for > advertised.listeners, > > which is in front of all my brokers? the flow for example > > > > broker1---------->| V > > broker2---------->| I > > broker3---------->| P > > > > I was under the impression that I can reach any broker I wanted (assuming > > that broker is 100% guaranteed to be healthy at all times, but it can > never > > be), and the broker coordination service will pass it onto the leader for > > that topicpartition. May be I am wrong. > > > > Has anyone done this successfully in production/staging/development? > > > > Regards, > > >
