feat: Add support for deterministic listener ports (based on broker ID) #183
+179
−49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an enhancement to the dynamic listeners capability, which adds this functionality:
--deterministic-listeners
flagnet.Listener
objects)net.Listener
and create a new one pointing at the new upstream listenerThis is built to support clusters where broker hostnames and ports are not deterministic. Specifically, multiple Confluent Cloud cluster types re-use broker IDs with randomly generated hostnames; this PR enables the Kafka-Proxy to work with these Confluent Cloud clusters.
@everesio any thoughts on this? Would love your input here!