[Feature] Integrated deployment of Eventmesh-Operator with nacos 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 its own nacos service in the k8s cluster.
### Describe the solution you'd like
eventmesh-operator needs to integrate its own nacos services 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
No files, tests, or entry points are identified in the issue. Start by locating the eventmesh-operator deployment manifests and reviewing how services are configured in the Kubernetes cluster. Confirm the required Nacos service integration and its expected deployment behavior before defining what done means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100