NiklasWagner commented on pull request #42: URL: https://github.com/apache/pulsar-helm-chart/pull/42#issuecomment-660087223
Ah that what you mean. We're actually using a ingress controller for that which is what most people are doing. We've many ingress resources from many different charts and our nginx ingress is taking care of that. We're not creating a LB for each ingress on our cloud provider. Additionally: Combining this in a single ingress resource would make it more complex for the ingress controller to correctly route the traffic. I think it would even make it impossible for us to work correctly since we're also using [external-dns](https://github.com/kubernetes-sigs/external-dns) to sync the hosts from the different ingress resources. ---------------------------------------------------------------- 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: us...@infra.apache.org
