Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

linjiemiao
Copy link

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

@liuruiyiyang liuruiyiyang changed the title 【ISSUE #54 #50】Operator multiple mq cluster && start sequence [ISSUE #54 #50] Operator multiple mq cluster && start sequence Sep 22, 2020
@liuruiyiyang liuruiyiyang added the enhancement New feature or request label Sep 22, 2020
@@ -38,6 +38,8 @@ spec:
size: 1
# nameServers is the [ip:port] list of name service
nameServers: ""
# rocketMQName is the rocketmq name, must equal to nameserver.spec.rocketMQName and topictransfer.spec.rocketMQName
Copy link
Contributor

@liuruiyiyang liuruiyiyang Sep 24, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so

@drivebyer
Copy link
Contributor

still need this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants