[GitHub] [incubator-pinot] xiangfu0 commented on issue #6940: Introduce `advertised.host` `advertised.port` support for cloud users

[GitBox <gi...@apache.org>]

xiangfu0 commented on issue #6940:
URL: https://github.com/apache/incubator-pinot/issues/6940#issuecomment-843742514


   > This problem brought up our attention when more users are under cloud deployment especially Kubernetes.
   > With such deployment, an external client is very hard to connect to Pinot as all the host/port returned from zookeeper/helix can only be resolved within the cloud environment itself.
   > E.g. with our helm deployment in k8s, if we open controller 9000 port, then the pinot client will find the broker address is `pinot-broker-0.pinot:8099`, which is unable to connect outside the k8s cluster.
   > 
   > So we need to introduce the concept of `advertised.host` and `advertised.port` so that when users try to connect to the pinot controller with the `external` flag on, then the given connection string should be using `<advertised.host>:<advertised.port>`. For internal communication, current `<host>:<port>` works fine.
   
   Some Ref from Kafka: https://www.confluent.io/blog/kafka-listeners-explained/
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org