@@ -30,11 +30,12 @@ by implementing one or more of these extension points.
30
30
31
31
<!--
32
32
You can specify scheduling profiles by running `kube-scheduler --config <filename>`,
33
- using the component config APIs
34
- ([`v1beta1`](https://pkg.go.dev/k8s.io/[email protected] /config/v1beta1?tab=doc#KubeSchedulerConfiguration)).
33
+ using the
34
+ [KubeSchedulerConfiguration (v1beta1)](/docs/reference/config-api/kube-scheduler-config.v1beta1/)
35
+ struct.
35
36
-->
36
37
你可以通过运行 ` kube-scheduler --config <filename> ` 来设置调度模板,
37
- 配置文件使用组件配置的 API ( [ ` v1alpha1 ` ] ( https://pkg.go.dev/k8s.io /kube-scheduler@v0.19.0/ config/ v1beta1?tab=doc#KubeSchedulerConfiguration ) ) 。
38
+ 使用 [ KubeSchedulerConfiguration (v1beta1) ] ( /docs/reference/config-api /kube-scheduler- config. v1beta1/ ) 结构体 。
38
39
39
40
<!-- A minimal configuration looks as follows: -->
40
41
最简单的配置如下:
@@ -285,11 +286,20 @@ extension points:
285
286
<!--
286
287
- `VolumeBinding` : Checks if the node has or if it can bind the requested
287
288
{{< glossary_tooltip text="volumes" term_id="volume" >}}.
288
- Extension points : ` PreFilter` , `Filter`, `Reserve`, `PreBind`.
289
+ Extension points : ` PreFilter` , `Filter`, `Reserve`, `PreBind`, `Score`.
290
+ {{< note >}}
291
+ ` Score` extension point is enabled when `VolumeCapacityPriority` feature is
292
+ enabled. It prioritizes the smallest PVs that can fit the requested volume
293
+ size.
294
+ {{< /note >}}
289
295
-->
290
296
- ` VolumeBinding` :检查节点是否有请求的卷,或是否可以绑定请求的卷。
291
-
292
- 实现的扩展点 : ` PreFilter` ,`Filter`,`Reserve`,`PreBind`。
297
+ 实现的扩展点 : ` PreFilter` 、`Filter`、`Reserve`、`PreBind` 和 `Score`。
298
+ {{< note >}}
299
+ 当 `VolumeCapacityPriority` 特性被启用时,`Score` 扩展点也被启用。
300
+ 它优先考虑可以满足所需卷大小的最小 PV。
301
+ {{< /note >}}
302
+
293
303
<!--
294
304
- `VolumeRestrictions` : Checks that volumes mounted in the node satisfy
295
305
restrictions that are specific to the volume provider.
@@ -389,13 +399,6 @@ that are not enabled by default:
389
399
390
400
实现的扩展点:`Score`。
391
401
<!--
392
- - `NodeResourceLimits` : Favors nodes that satisfy the Pod resource limits.
393
- Extension points : ` PreScore` , `Score`.
394
- -->
395
- - ` NodeResourceLimits` :选择满足 Pod 资源限制的节点。
396
-
397
- 实现的扩展点:`PreScore`,`Score`。
398
- <!--
399
402
- `CinderVolume` : Checks that OpenStack Cinder volume limits can be satisfied
400
403
for the node.
401
404
Extension points : ` Filter` .
@@ -507,6 +510,9 @@ only has one pending pods queue.
507
510
<!--
508
511
* Read the [kube-scheduler reference](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/)
509
512
* Learn about [scheduling](/docs/concepts/scheduling-eviction/kube-scheduler/)
513
+ * Read the [kube-scheduler configuration (v1beta1)](/docs/reference/config-api/kube-scheduler-config.v1beta1/) reference
510
514
-->
511
515
* 阅读 [kube-scheduler 参考](/zh/docs/reference/command-line-tools-reference/kube-scheduler/)
512
516
* 了解[调度](/zh/docs/concepts/scheduling-eviction/kube-scheduler/)
517
+ * 阅读 [kube-scheduler 配置 (v1beta1)](/zh/docs/reference/config-api/kube-scheduler-config.v1beta1/) 参考
518
+
0 commit comments