-
Notifications
You must be signed in to change notification settings - Fork 277
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
WIP: Implementation for Topology Aware Scheduling [prototype for testing e2e, DO NOT MERGE] #3218
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mimowo 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 |
/test all |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
cc @PBundyra please check the "Special notes for your reviewer". |
e51c920
to
b187bdf
Compare
/test all |
/test all |
/test all |
eff20d6
to
1706fba
Compare
/test all |
/test all |
/test all |
38264dd
to
c7aea4c
Compare
/test all |
/test all |
/test all |
/test all |
/test all |
PR needs rebase. 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. |
/close |
@mimowo: Closed this PR. 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. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Part of #2724
Special notes for your reviewer:
This is an e2e prototype of the feature. I used it to evaluate if there are no gaps in the KEP. There are no bigger gaps, but doing the prototype I identified a couple of issues that could be improved in the design. I will submit a KEP update PR.
Comments are welcome, but the actual code to merge will be in separate smaller PRs.
Things which are still missing in the PR:
Does this PR introduce a user-facing change?