operator v1: create internal kafka api port #205
Merged
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.
currently in cloud, we use the full list of brokers and pass it around to various service making use of it, e.g. kafka connect.
however, this is completely ignoring the service discovery feature of the kafka api: bootstrap servers.
there is already a ClusterIP service for this purpose. However, it does not include kafka API. this patch adds kafka API to the ClusterIP service.
internal usage can now be done via the $name-cluster service on port 9092, if configured. tested on a cloud cluster.
the new usage internally is:
(From debug pod in same namespace):