lhotari commented on issue #423: URL: https://github.com/apache/pulsar-helm-chart/issues/423#issuecomment-1895605385
Ingress probably wouldn't make sense for Pulsar brokers, at least for the binary protocol. For the Pulsar Admin API that would be a feasible approach. You could use k8s node ports and Pulsar's "advertisedListeners" feature: https://pulsar.apache.org/docs/3.1.x/concepts-multiple-advertised-listeners/#advertised-listeners However, configuring that would require some special customization and integration to make it work with a Pulsar k8s deployment. Another possibility is the SNI proxy feature and use a proxy that supports SNI proxying (for example Apache Traffic server or Nginx): https://pulsar.apache.org/docs/3.1.x/concepts-proxy-sni-routing/ -- 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. To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
