RockteMQ-AI commented on issue #240: URL: https://github.com/apache/rocketmq-operator/issues/240#issuecomment-5395018116
**Issue Evaluation** Category: `question` The current RocketMQ Operator is designed for single-cluster management within a namespace. Multi-cluster deployment (managing RocketMQ clusters across different namespaces) is not natively supported in the current operator design. The issue you encountered (Broker getting NameServer address from a different namespace) is expected — the operator generates `NAMESRV_ADDR` based on its own namespace's NameServer service. **Workaround:** Deploy one operator instance per namespace, each managing its own RocketMQ cluster. This provides namespace isolation and avoids cross-namespace service discovery conflicts. **Feature request:** Multi-cluster support would require the operator to be namespace-aware and manage cluster resources per-namespace. This is a valid enhancement but requires significant design work. --- *Automated evaluation by github-manager* -- 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]
