KAFKA-10478: Allow duplicated ports in advertised.listeners (#9281)
Remove the requirement for unique port numbers for the advertised.listener parameters. This restriction makes for the listeners parameter but there's not reason to apply the same logic for advertised.listeners. Being able to do this opens possibilities for some practical applications when using Kerberos authentication. For example, when configuring Kafka using Kerberos authentication and a Load Balancer we need to have two SASL_SSL listeners: (A) one running with the kafka/hostname principal and (B) another using kafka/lb_name, which is necessary for proper authentication when using the LB FQDN. After bootstrap, though, the client receives the brokers' addresses with the actual host FQDNs advertised by the brokers. To connect to the brokerd using the hostnames the client must connect to the listener A to be able to authenticate successfully with Kerberos. Author: Andre Araujo <asdaraujo@gmail.com> Reviewers: Mickael Maison <mickael.maison@gmail.com>, Viktor Somogyi-Vass <viktorsomogyi@gmail.com>, Tom Bentley <tbentley@redhat.com>
显示
- core/src/main/scala/kafka/server/KafkaConfig.scala 16 个添加, 12 个删除core/src/main/scala/kafka/server/KafkaConfig.scala
- core/src/main/scala/kafka/utils/CoreUtils.scala 8 个添加, 2 个删除core/src/main/scala/kafka/utils/CoreUtils.scala
- core/src/test/scala/unit/kafka/server/KafkaConfigTest.scala 23 个添加, 10 个删除core/src/test/scala/unit/kafka/server/KafkaConfigTest.scala
加载中
想要评论请 注册 或 登录