Skip to content

Commit dfda271

Browse files
authored
Update kube-scheduler.md (#38264)
* Update kube-scheduler.md A clearer way to write this paragraph explaining the scheduler. Previous version: For every newly created pod or other unscheduled pods, kube-scheduler selects an optimal node for them to run on. However, every container in pods has different requirements for resources and every pod also has different requirements. Therefore, existing nodes need to be filtered according to the specific scheduling requirements. Proposed version: Kube-scheduler selects an optimal node to run newly created or not yet scheduled (unscheduled) pods. Since containers in pods, and pods themselves have different requirements, existing nodes need to be filtered according to the specific scheduling requirements. * Update kube-scheduler.md I tried merging both our versions to make it a bit more concise, since feasibility is discussed in the subsequent paragraphs.
1 parent 2860712 commit dfda271

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

content/en/docs/concepts/scheduling-eviction/kube-scheduler.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,12 @@ is the default scheduler for Kubernetes and runs as part of the
3232
kube-scheduler is designed so that, if you want and need to, you can
3333
write your own scheduling component and use that instead.
3434

35-
For every newly created pod or other unscheduled pods, kube-scheduler
36-
selects an optimal node for them to run on. However, every container in
37-
pods has different requirements for resources and every pod also has
38-
different requirements. Therefore, existing nodes need to be filtered
39-
according to the specific scheduling requirements.
35+
Kube-scheduler selects an optimal node to run newly created or not yet
36+
scheduled (unscheduled) pods. Since containers in pods - and pods themselves -
37+
can have different requirements, the scheduler filters out any nodes that
38+
don't meet a Pod's specific scheduling needs. Alternatively, the API lets
39+
you specify a node for a Pod when you create it, but this is unusual
40+
and is only done in special cases.
4041

4142
In a cluster, Nodes that meet the scheduling requirements for a Pod
4243
are called _feasible_ nodes. If none of the nodes are suitable, the pod

0 commit comments

Comments
 (0)