fix: minimum feasible nodes 50->100
That the current `minFeasibleNodesToFind` is 100 instead of 50 (in docs). See `kubernetes/pkg/scheduler/schedule_one.go`.pull/46994/head
parent
5000977706
commit
44460b3ee3
|
@ -103,9 +103,9 @@ percentageOfNodesToScore: 50
|
|||
|
||||
`percentageOfNodesToScore` must be a value between 1 and 100 with the default
|
||||
value being calculated based on the cluster size. There is also a hardcoded
|
||||
minimum value of 50 nodes.
|
||||
minimum value of 100 nodes.
|
||||
|
||||
{{< note >}}In clusters with less than 50 feasible nodes, the scheduler still
|
||||
{{< note >}}In clusters with less than 100 feasible nodes, the scheduler still
|
||||
checks all the nodes because there are not enough feasible nodes to stop
|
||||
the scheduler's search early.
|
||||
|
||||
|
|
Loading…
Reference in New Issue