youurayy edited a comment on issue #4687: Publish Pulsar Helm chart on the official Helm Charts repository URL: https://github.com/apache/pulsar/issues/4687#issuecomment-549307948 Here's how (difficult it is) to currently achieve direct Pulsar Broker access on Kubernetes: 1. change Broker deployment to a `StatefulSet` (go by how the Bookkeeper deploy is spec'd) 2. change Broker service to type `NodePort` and add `externalTrafficPolicy: Local` 3. comment out the line `clusterIP: None` from the Broker service 4. change *both* Broker internal and external `pulsar://` ports to `30002` in `values.yaml` - this involves adding a `nodePort: 30002` line 5. add `brokerServicePort: "30002"` to Broker's configData in `values.yaml` 6. change `advertisedAddress` in Broker deploy from `status.podIP` to `status.hostIP` 7. use `pulsar://your-k8s-node1-or-ip:30002,your-k8s-node1-or-ip:30002/` type of URL for your Pulsar client This way you can access your Kuberenetes Pulsar Brokers from the outside of the cluster and the topic redirections sent from Brokers to the Clients will work.
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
