...

Current state: Under Discussion

Discussion thread:here [Change the link from the KIP proposal email archive to your own email thread] here

JIRA: here [Change the link from KAFKA-66691 to your own ticket]

Motivation

The purpose of the change is to accommodate environments without proper DNS support, when KafkaProducer or KafkaConsumer tries to connect to Kafka brokers that are inside another network.

...

The KIP is fully backward-compatible. If no Redirector configuration specified, Selector will work in the same way.

Rejected Alternatives

...

• Advertised listeners configuration is not easy to use in environment like OpenShift, when pods are periodically restarted and getting assigned IPs and DNS names. This will require the deployment script to manipulate each broker configuration on pod startup, which is hard process, if possible at all. Each replica should have a particular configuration assigned in both Kubernetes and broker that is not always possible, while easier to control the forwarding process on Kafka Client itself, allowing testing from IDE without deploying the code into Kubernetes.