-
Notifications
You must be signed in to change notification settings - Fork 40.9k
Moving Scheduler interfaces to staging: Move Code and Status from pkg/scheduler/framework to k8s.io/kube-scheduler/framework #132087
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
Moving Scheduler interfaces to staging: Move Code and Status from pkg/scheduler/framework to k8s.io/kube-scheduler/framework #132087
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
Hi @ania-borowiec. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/cc @macsko @sanposhiho |
/ok-to-test |
ab1761c
to
7140f94
Compare
Thanks @sanposhiho ! I cleaned up labels and squashed the commits. |
/cc @x13n do you think you could review this change on behalf of Cluster Autoscaler? |
@ania-borowiec: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
7140f94
to
ee8c265
Compare
/approve For autoscaler_contract |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ania-borowiec, macsko, sanposhiho, x13n The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm As we have all approvals |
LGTM label has been added. Git tree hash: bf411404d57a37c948a116f5d782edd91f12f0bf
|
/remove-label api-review /unhold |
@sanposhiho: Those labels are not set on the issue: In response to this:
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. |
/remove-kind api-change |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This is part of a larger change that moves interfaces and type and func defiinitions to the staging repo "k8s.io/kube-scheduler", to allow users for importing scheduler framework interfaces without importing k/k repo.
This PR moves structs Code and Status from k/k to the staging repo
Which issue(s) this PR fixes:
Part of #89930
Special notes for your reviewer:
Moving this in a separate PR, since the PR moving everything is just too big to be reviewed
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: