Hello!

I understand that advertised.listeners in a KRaft-backed cluster are now
only a static configuration, but I was wondering about the reasoning behind
this decision?

I suspect it has something to do with not publicising the listeners for the
controllers, but I do not understand why we can't just filter those out?

For example, I am able to start a node which is both a broker and a
controller with

listeners=PLAINTEXT://:9092,CONTROLLER://:9093
advertised.listeners=PLAINTEXT://localhost:9092

and I am then able to communicate with port 9093 from the same machine.

Any help would be greatly appreciated!

Best,
Christo

Reply via email to