-
Notifications
You must be signed in to change notification settings - Fork 891
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
feat: cluster-level resource scheduling suspend and resume capabilities #5937
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @Monokaix! It looks like this is your first PR to karmada-io/karmada 🎉 |
c4d5f12
to
08407d6
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5937 +/- ##
==========================================
+ Coverage 48.15% 48.21% +0.05%
==========================================
Files 664 664
Lines 54803 54886 +83
==========================================
+ Hits 26393 26464 +71
- Misses 26693 26702 +9
- Partials 1717 1720 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Monokaix <changxuzheng@huawei.com>
Signed-off-by: Monokaix <changxuzheng@huawei.com>
Signed-off-by: Monokaix <changxuzheng@huawei.com>
What type of PR is this?
/kind api-change
/kind feature
What this PR does / why we need it:
Add rb suspension capability, background: #5690
Which issue(s) this PR fixes:
Fixes #5690
Special notes for your reviewer:
It extends the Suspension fileds and support rb susupend and resume, mostly like the previous issue #5217 and PRs implemented in it.
Does this PR introduce a user-facing change?: