-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Set "Multi Scheduling Profiles" to "implementable" #1483
Set "Multi Scheduling Profiles" to "implementable" #1483
Conversation
485ef34
to
1b4685f
Compare
/sig testing |
/assign @liggitt for architecture /assign @Huang-Wei for scheduling |
38fdc91
to
a32704c
Compare
@liggitt Friendly ping |
|
||
TODO | ||
- [ ] New `v1alpha2` ComponentConfig API, with conversion from `v1alpha1` and defaults. | ||
- [ ] New feature gate. |
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.
@liggitt do we really need a feature gate? it looks to me like this is mostly a refactoring, and I am not sure a feature gate helps too much in gating a refactoring.
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.
True. Given that users have to explicitly use kubescheduler.config.k8s.io/v1alpha2
API, having a feature gate just adds a redundant step. The API is a gate on its own. Unless we have to adhere to some standard practice?
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.
I removed the feature gate and added a note in the following paragraph.
9af47a7
to
85a4c67
Compare
proposed component config lgtm |
/hold @Huang-Wei please take a final look, the deadline is today I think. |
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.
Thanks @alculquicondor.
Please fix the typo and use the chance to squash the commits.
@@ -158,14 +158,21 @@ type KubeSchedulerProfile struct { | |||
} | |||
``` | |||
|
|||
Note that we remove `AlgorithmSource` from the new API. It's functionality becomes redundant to |
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.
Its.
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.
Good catch. Done.
85a4c67
to
ead3e26
Compare
Also specify validation of Plugins.QueueSort and remove AlgorithmSource. Signed-off-by: Aldo Culquicondor <[email protected]>
ead3e26
to
bf978ca
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, alculquicondor, Huang-Wei 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 |
Add Test Plan and Alpha Graduation criteria.
Also: