Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is there a per-broker service for external (outside-cluster) access? #178

Open
prithviramesh opened this issue May 23, 2018 · 1 comment

Comments

@prithviramesh
Copy link

prithviramesh commented May 23, 2018

Our use case involves creating an Ingress that routes external access to our n-broker Kafka cluster. Currently, (without changing the Ingress to a "fan-out" Ingress) we can only map the Ingress to one of the external services which maps to one specific broker pod. What we actually want is our Ingress to load balance the producer to write to a topic that is partitioned on each of the n brokers.

@solsson
Copy link
Contributor

solsson commented May 24, 2018

It's by design, Kafka design. Clients are very much aware of broker topology. See for example #13 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants