RockteMQ-AI commented on issue #240: URL: https://github.com/apache/rocketmq-operator/issues/240#issuecomment-5487022416
**Issue Evaluation** Category: `question` Deploying multiple RocketMQ clusters in different namespaces with a single operator is a known challenge. The operator currently uses cluster-scoped resources, which means the NAMESRV_ADDR may resolve to a service in another namespace. To work around this: 1. Deploy separate operator instances per namespace, or 2. Use namespace-scoped RBAC and ensure each operator watches only its own namespace via `--namespace` flag 3. Explicitly set `.spec.nameServers` to the in-namespace NameServer service FQDN (e.g., `namesrv-svc.rocketmq-ns-1.svc.cluster.local:9876`) The broker registration issue you observed when setting `.spec.nameServers` manually may be related to how the operator resolves the NameServer address for broker registration. --- *Automated evaluation by RockteMQ-AI* -- 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]
