[ISSUE #54 #50] Operator multiple mq cluster && start sequence

[linjiemiao]

1. ensure rocketmq-operator can operator more than one rocketmq cluster;
2. make sure nameserver must ready before broker cluster.

[liuruiyiyang]

We can not ensure users set insistent name correctly, is there a better way to do this?

[linjiemiao]

I did this because we don't have a rocketmq resource as the parent resource of the broker and nameserver. Without a common parent controller, we can only specify the connection of the child resource in the spec. So I hope to add a rocketmq api.

[liuruiyiyang]

In that case should we add rocketmq higher level api before this PR?

[linjiemiao]

I think so

[drivebyer]

still need this

[RockteMQ-AI]

⚠️ Merge conflict detected

This PR has conflicts with the base branch and cannot be merged. Please rebase or merge the base branch into your branch and resolve the conflicts:

git fetch origin
git checkout issue-54-codereview
git rebase origin/main
# resolve conflicts, then:
git push --force-with-lease

This is a one-time reminder. Feel free to @mention me for a re-review after conflicts are resolved.

---

Automated notification by github-manager-bot