aweiri1 commented on issue #24819: URL: https://github.com/apache/pulsar/issues/24819#issuecomment-3374866759
@lhotari 1. Yes, I am using the default configuration and it is set to true. 2. the admin connectivity works both ways by running the below command on both clusters and getting the same output: - `url -s http://<load-balancer-ip>:8080/admin/v2/clusters ["pulsar-okd1","pulsar-talos"]` 3. yes, when spinning up the clusters via helm charts, I do a clusters update command to update the clusters to use the load balancer external IP address (rather than the kubernetes dns address).: - `bin/pulsar-admin clusters update pulsar-talos \ --broker-url pulsar://load-balancer-ip:6650 \ --url http://<load-balancer-ip:8080 \` I do this for both pulsar-talos and pulsar-okd1 clusters. After I spin up both clusters via the helm charts, and do a clusters list (on either cluster) both clusters already exists there (pulsar-talos and pulsar-okd1). This is because of the shared global config store, so the clusters already know about each other and exist on each other when doing the clusters list command. So I never have to do a `clusters create` just a `clusters update`. I restart the brokers after the update change. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
