You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2024/06/28 03:44:00 UTC
[jira] [Resolved] (KAFKA-16781) Expose advertised.listeners in controller node
[ https://issues.apache.org/jira/browse/KAFKA-16781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Chen resolved KAFKA-16781.
-------------------------------
Fix Version/s: 3.9.0
Resolution: Fixed
> 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++
> Fix For: 3.9.0
>
>
> 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)