Hi, I've got a question regarding multiple tenants on Kubernetes deployments of Pinot. Given, • the clients of our pinot cluster need to be able to reach the appropriate broker for the table that they are querying from outside the kubernetes cluster • brokers can be rebalanced, and we might have multiple brokers for any one tenant • as far as I can tell, the controller will only give you the cluster-local URL of the appropriate broker when asked about where to find a table How can I set up a single URL for the whole cluster, or a single URL for each tenant (either case is fine) for clients outside our kubernetes cluster to access the correct broker? I do not see anything detailing a way to allow the controller to advertise the cluster-external broker URL instead of the cluster-local one. If it were able to do this, it would likely be sufficient for our use case.

Great question. What you need is something like a proxy that can be tenant aware and load balance across tenant specific brokers. There's one available, but not in open source.

Gotcha. That is something that we were considering. It would have been nice if it was something that could be entirely configuration-driven.

Having said that, if you do introduce a common entry point, all traffic will go through it. And that could be problematic if some tenants were fetching huge amounts of data.