Skip to content

[ISSUE #135]Support Broker clusters in Conntroller mode#136

Merged
caigy merged 2 commits intoapache:masterfrom
caigy:issue-135
Nov 3, 2022
Merged

[ISSUE #135]Support Broker clusters in Conntroller mode#136
caigy merged 2 commits intoapache:masterfrom
caigy:issue-135

Conversation

@caigy
Copy link
Copy Markdown
Contributor

@caigy caigy commented Oct 19, 2022

What is the purpose of the change

fix #135

Brief changelog

Add CRD and controller logic for DLedger Controller, which enables auto-switching broker clusters.

Verifying this change

Please go through this checklist to help us incorporate your contribution quickly and easily.

Notice: It would be helpful if you could finish the following checklist (the last one is not necessary) before request the community to review your PR.

  • Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
  • Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Check RBAC rights for Kubernetes roles.
  • Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist.
  • Run make docker-build to build docker image for operator, try your changes from Pod inside your Kubernetes cluster, not just locally. Also provide screenshots to show that the RocketMQ cluster is healthy after the changes.
  • Before committing your changes, remember to run make manifests to make sure the CRD files are updated.
  • Update documentation if necessary.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

NameServers string `json:"nameServers,omitempty"`
// ClusterMode defines the way to be a broker cluster, valid values can be one of the following:
// STATIC(default), CONTROLLER, CONTAINER
ClusterMode string `json:"clusterMode,omitempty"`
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What does it mean when the value of this variable is CONTAINER?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This value is for Broker Container mode: https://github.com/apache/rocketmq/blob/develop/docs/cn/BrokerContainer.md

If this function is not implemented in version 0.4.0, we'd better deal with the boundaries well

@caigy caigy added this to the 0.4.0 milestone Nov 3, 2022
@caigy caigy merged commit bad939d into apache:master Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support auto-switching cluster mode for brokers in RocketMQ 5.x

2 participants