-
Notifications
You must be signed in to change notification settings - Fork 548
remove useless scheme in coscheduling client #882
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
base: master
Are you sure you want to change the base?
remove useless scheme in coscheduling client #882
Conversation
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: KunWuLuan 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 |
✅ Deploy Preview for kubernetes-sigs-scheduler-plugins canceled.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I missing something? this seems the same change as #881 - adding cache
I split that pr to 2 prs, each of them contains one commit. |
I had the same question... this PR looks the same as #881. The changes are valid. Per #881 (comment), @KunWuLuan could you help consolidate changes needed for all plugins in one PR? |
@Huang-Wei @ffromani Sorry I wanted to remove the useless scheme in this pr and it seems that I have some mistakes with the commits. I will correct this pr today. |
cca2c51
to
1488908
Compare
Because the reason about network, git push failed last time. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
In #881, I added a cache for client in coscheduling plugin, this may cause listing of core resources like pods and nodes.
Client in coscheduling will only be used to get and list podgroups. Remove these code can save memory by preventing the listing of core resources like pods and nodes any more.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?