Details
-
Test
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Kafka currently supports named listeners, where you can have two or more listeners with the same security protocol but different names. Current KafkaService implementation, however, wouldn't allow that, since listeners in port_mappings are keyed by security_protocol, so there's 1-1 relationship. Kafka clients in system tests use bootstrap_servers() method, which also accepts security_protocol, as a way to pick a port to talk to kafka.
The scope of this jira is to refactor KafkaService to support named listeners, specifically two things - ability to have custom-named listeners and ability to have several listeners with the same security protocol.
Attachments
Issue Links
- links to