-
Notifications
You must be signed in to change notification settings - Fork 639
[ISSUE #4694] Component initialization order adjustment, add resource constraints. #4693
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
Conversation
…ponent initialization order rules and DNS.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4693 +/- ##
============================================
+ Coverage 17.38% 17.55% +0.16%
- Complexity 1757 1778 +21
============================================
Files 797 797
Lines 29776 29871 +95
Branches 2573 2582 +9
============================================
+ Hits 5177 5243 +66
- Misses 24121 24145 +24
- Partials 478 483 +5 ☔ View full report in Codecov by Sentry. |
|
May I ask that is this PR working in progress or ready for review? |
This pr is ready for review and has been tested with pr #4727. The image used at this stage is built on this basis. |
eventmesh-operator/config/samples/eventmesh_v1_connectors_rocketmq.yaml
Outdated
Show resolved
Hide resolved
…source constraints. (apache#4693) * resources describes the compute resource requirements and limits 、component initialization order rules and DNS. * add license and update runtime resources * update runtime_controller.go * update * deployment operator, commands simplified. * update * update * update * update
…ponent initialization order rules and DNS.
Fixes #4694 .
Motivation
Component initialization order adjustment, add resource constraints.
Modifications
Component initialization order adjustment, add resource constraints.
Documentation