[
https://issues.apache.org/jira/browse/KAFKA-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038324#comment-17038324
]
Sergey Korytnikov commented on KAFKA-6669:
------------------------------------------
[~gokul2411s], I didn't find enough interest among Kafka dev list members in
this proposal to maintain a discussion and proceed with voting. To my
knowledge, we couldn't find any workaround for Kafka cluster at the time,
deployed on OpenShift MacOS. This feature has a value for development testing
mostly and not for production as usually Kafka brokers may not be accessed from
outside of Kubernetes cluster.
> KIP-271: Add NetworkClient redirector
> -------------------------------------
>
> Key: KAFKA-6669
> URL: https://issues.apache.org/jira/browse/KAFKA-6669
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Reporter: Sergey Korytnikov
> Priority: Major
>
> "KIP-271 Add NetworkClient redirector" purposes the change to accommodate
> environments without proper DNS support, when KafkaProducer or KafkaConsumer
> tries to connect to Kafka brokers that are inside another network.
> Currently, Kafka client connection fails with
> "[java.io|http://java.io/].IOException: Can't resolve address" after Kafka
> cluster metadata is updated with internal DNS names of brokers, unreachable
> by Client. The example of such configuration might be a Java Client calling
> Kafka Cluster from outside of Kubernetes cluster or AWS network.
> The KIP improves NetworkClient to redirect the call to alternative network
> address and provides developers with additional Configurable interface to
> specify redirection rules.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
