lhotari commented on issue #24819: URL: https://github.com/apache/pulsar/issues/24819#issuecomment-3561949519
Before enabling geo-replication, you should validate the connection between the clusters, so that you can produce messages into a topic from the source cluster to the target cluster. You can use the command line tool `PULSAR_CLIENT_CONF=$PWD/myconfig.conf /pulsar/bin/pulsar-client produce` to perform this test, where you'd put the client's configuration in the `myconfig.conf` file. You can copy the `/pulsar/conf/client.conf` to `myconfig.conf` and then modify the values. In the Apache Pulsar Helm chart, there isn't a great solution from security perspective for authorization and authentication across the clusters. If you use the JWT token auth, the private key would have to be shared. This is not great since rotating the keys is very hard without significant service impact. The more recommended approach is to use OIDC authentication and there's support in the Helm chart, but there isn't much docs about how to configure it with multiple clusters. -- 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]
