Skip to content

Commit d932e33

Browse files
committed
[zh-cn] Sync scheduling-framework.md and topology-spread-constraints.md
1 parent b3e0ed2 commit d932e33

File tree

2 files changed

+33
-6
lines changed

2 files changed

+33
-6
lines changed

content/zh-cn/docs/concepts/scheduling-eviction/scheduling-framework.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -255,6 +255,31 @@ scores from all plugins according to the configured plugin weights.
255255
[标准化评分](#normalize-scoring)阶段之后,
256256
调度器将根据配置的插件权重合并所有插件的节点分数。
257257

258+
<!--
259+
#### Capacity scoring {#scoring-capacity}
260+
261+
{{< feature-state feature_gate_name="StorageCapacityScoring" >}}
262+
263+
The feature gate `VolumeCapacityPriority` was used in v1.32 to support storage that are
264+
statically provisioned. Starting from v1.33, the new feature gate `StorageCapacityScoring`
265+
replaces the old `VolumeCapacityPriority` gate with added support to dynamically provisioned storage.
266+
When `StorageCapacityScoring` is enabled, the VolumeBinding plugin in the kube-scheduler is extended
267+
to score Nodes based on the storage capacity on each of them.
268+
This feature is applicable to CSI volumes that supported [Storage Capacity](/docs/concepts/storage/storage-capacity/),
269+
including local storage backed by a CSI driver.
270+
-->
271+
#### 容量打分 {#scoring-capacity}
272+
273+
{{< feature-state feature_gate_name="StorageCapacityScoring" >}}
274+
275+
在 v1.32 中,特性门控 `VolumeCapacityPriority` 被用于支持静态制备的存储。
276+
从 v1.33 开始,新的特性门控 `StorageCapacityScoring` 取代了旧的 `VolumeCapacityPriority`
277+
并新增了对动态制备存储的支持。
278+
启用 `StorageCapacityScoring` 后,kube-scheduler 中的 VolumeBinding 插件功能将进行扩展,
279+
根据每个节点上的存储容量对节点进行打分。
280+
该特性适用于支持[存储容量](/zh-cn/docs/concepts/storage/storage-capacity/)的 CSI 卷,
281+
包括由 CSI 驱动程序支持的本地存储。
282+
258283
<!--
259284
### NormalizeScore {#normalize-scoring}
260285
-->

content/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -316,11 +316,12 @@ your cluster. Those fields are:
316316

317317
{{< note >}}
318318
<!--
319-
The `nodeAffinityPolicy` is a beta-level field and enabled by default in 1.26. You can disable it by disabling the
319+
The `nodeAffinityPolicy` became beta in 1.26 and graduated to GA in 1.33.
320+
It's enabled by default in beta, you can disable it by disabling the
320321
`NodeInclusionPolicyInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
321322
-->
322-
`nodeAffinityPolicy` 1.26 中默认启用的一个 Beta 级别字段
323-
你可以通过禁用 `NodeInclusionPolicyInPodTopologySpread`
323+
`nodeAffinityPolicy` 1.26 版本中进入 Beta 阶段,并在 1.33 版本中升级为 GA(正式可用)
324+
该功能在 Beta 阶段默认启用,你可以通过禁用 `NodeInclusionPolicyInPodTopologySpread`
324325
[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来禁用此字段。
325326
{{< /note >}}
326327

@@ -341,11 +342,12 @@ your cluster. Those fields are:
341342

342343
{{< note >}}
343344
<!--
344-
The `nodeTaintsPolicy` is a beta-level field and enabled by default in 1.26. You can disable it by disabling the
345+
The `nodeTaintsPolicy` became beta in 1.26 and graduated to GA in 1.33.
346+
It's enabled by default in beta, you can disable it by disabling the
345347
`NodeInclusionPolicyInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
346348
-->
347-
`nodeTaintsPolicy` 是一个 Beta 级别字段,在 1.26 版本默认启用
348-
你可以通过禁用 `NodeInclusionPolicyInPodTopologySpread`
349+
`nodeTaintsPolicy` 在 1.26 版本中进入 Beta 阶段,并在 1.33 版本中升级为 GA(正式可用)
350+
该功能在 Beta 阶段默认启用,你可以通过禁用 `NodeInclusionPolicyInPodTopologySpread`
349351
[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来禁用此字段。
350352
{{< /note >}}
351353

0 commit comments

Comments
 (0)