RockteMQ-AI commented on issue #240: URL: https://github.com/apache/rocketmq-operator/issues/240#issuecomment-5364746640
**Issue Evaluation** Category: `question` This is a usage question about multi-cluster deployment with RocketMQ Operator. To deploy multiple RocketMQ clusters in different namespaces using a single Operator instance: 1. The Operator is cluster-scoped by default — it can watch all namespaces. Ensure the RBAC `ClusterRole` has permissions for the target namespaces. 2. Each namespace should have its own `Rocketmq` CR (NameServer + Broker). The key issue you're seeing (broker getting NAMESRV_ADDR from another namespace) is because the Operator injects the NameServer address based on label selectors. Make sure each Broker CR's `.spec.nameServers` explicitly points to the correct NameServer service in the same namespace. 3. If `.spec.nameServers` is not working as expected, this may be a bug in the Operator's environment variable injection logic. Please share the Broker CR YAML and the Operator version for further investigation. --- *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]
