-
Notifications
You must be signed in to change notification settings - Fork 14.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
Add Scheduling Configuration reference doc #21437
Add Scheduling Configuration reference doc #21437
Conversation
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 9ed3f42 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5f0489b67e14fa000717a31d |
f8accec
to
1c3a600
Compare
/sig scheduling |
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.
Some early / informal feedback
1c3a600
to
0fb8777
Compare
Thanks all for the feedback. This PR is still WIP, but section header and id is now in its intended state. |
/milestone 1.19 |
Hi @alculquicondor 👋 , Please rebase your PR to avoid major merge conflicts :) Thanks! |
0fb8777
to
023782d
Compare
/assign @Huang-Wei cc @pancernik |
023782d
to
86cbfe2
Compare
86cbfe2
to
c890227
Compare
Built from the existing Scheduling Profiles doc. Signed-off-by: Aldo Culquicondor <[email protected]>
c890227
to
72090c9
Compare
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.
Markdown looks OK to me.
The new text:
The
KubeSchedulerConfiguration
is a configuration API forkube-scheduler
that can be provided as a file via--config
command line flag.
could be a bit confusing to readers, but if this merges as-is I'm fine with that.
@alculquicondor you can revise again or move forward towards a technical LGTM and either approach works for me.
Signed-off-by: Aldo Culquicondor <[email protected]>
Latest revision looks good to me. |
I'm not sure who is reviewing for SIG Scheduling. I think that this should have technical review (and I also hope that this is easy to review). @kubernetes/sig-scheduling-pr-reviews this is |
|
@ahg-g mind giving lgtm? |
/lgtm Tin, I already reviewed the PR |
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.
Sry for the late review. Some nits.
@@ -33,33 +44,57 @@ extension points: | |||
sort pending Pods in the scheduling queue. Exactly one queue sort plugin | |||
may be enabled at a time. | |||
1. `PreFilter`: These plugins are used to pre-process or check information | |||
about a Pod or the cluster before filtering. | |||
about a Pod or the cluster before filtering. They can mark a pod as | |||
unschedulable. | |||
1. `Filter`: These plugins are the equivalent of Predicates in a scheduling |
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 will submit another PR finishing the PostFilter
part.
weight: 1 | ||
``` | ||
|
||
You can use `*` as name in the disabled array to disable all default plugins |
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.
You can use `*` as name in the disabled array to disable all default plugins | |
You can use `*` as name in the disabled array to disable all default plugins |
/assign |
VolumeBinding changes LGTM |
score: | ||
disabled: | ||
- name: '*' | ||
``` |
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.
Would it make sense to explain this example? For example by adding a paragraph:
The example above will configure
kube-scheduler
to run two schedulers: the default one andno-scoring-scheduler
with thescore
extension point disabled for all plugins.
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 suggestion
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.
this is interesting, so are we saying we will be able to use the same scheduler binary to act as two different schedulers based on the scheduler field in the Pod ?
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.
Correct.
Signed-off-by: Aldo Culquicondor <[email protected]>
LGTM |
@savitharaghunathan or @sftim anything else for approval? |
Changes since #21437 (comment) look good to me |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: savitharaghunathan 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 |
kubernetes/enhancements#1451
kubernetes/enhancements#785
Updates include:
v1alpha2
VolumeBinding
extension points