[Feature] Integrated deployment of EventMesh-Operator and rocketmq in a k8s cluster
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 658
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 52
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Enhancement Request
eventmesh-operator needs to integrate and deploy its own rocketmq in the k8s cluster.
### Describe the solution you'd like
now, eventmesh-operator can already deploy runtime, rocketmq-connector components in k8s cluster, eventmesh-operator needs to integrate its own rocketmq service in the k8s cluster.
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [ ] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) *
Contributor guide
Research direction
Start by reading the existing eventmesh-operator support for deploying runtime and rocketmq-connector components in a Kubernetes cluster. Compare their deployment flow with the requested integrated RocketMQ service, then clarify the operator behavior and integration boundaries before implementation. Done means the operator can deploy and manage its own RocketMQ service alongside those components in the cluster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes
- Domain
- devops, distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100