[
https://issues.apache.org/jira/browse/KAFKA-16781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860554#comment-17860554
]
Gantigmaa Selenge commented on KAFKA-16781:
-------------------------------------------
[~showuon] I think we can close this issue as it's already implemented in
[https://github.com/apache/kafka/pull/16235]
> Expose advertised.listeners in controller node
> ----------------------------------------------
>
> Key: KAFKA-16781
> URL: https://issues.apache.org/jira/browse/KAFKA-16781
> Project: Kafka
> Issue Type: Improvement
> Reporter: Luke Chen
> Assignee: Gantigmaa Selenge
> Priority: Major
> Labels: need-kip, newbie, newbie++
>
> After
> [KIP-919|https://cwiki.apache.org/confluence/display/KAFKA/KIP-919%3A+Allow+AdminClient+to+Talk+Directly+with+the+KRaft+Controller+Quorum+and+add+Controller+Registration],
> we allow clients to talk to the KRaft controller node directly. But unlike
> broker node, we don't allow users to config advertised.listeners for clients
> to connect to. Without this config, the client cannot connect to the
> controller node if the controller is sitting behind NAT network while the
> client is in the external network.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
