[zh-cn]sync manage-resources-containers assign-pod-node

Signed-off-by: xin.li <xin.li@daocloud.io>

Author: my-git9

content/zh-cn/docs/concepts/configuration/manage-resources-containers.md

@@ -211,21 +211,24 @@ resource requests/limits of that type for each container in the Pod.
 {{< feature-state feature_gate_name="PodLevelResources" >}}
 
 <!--
-Starting in Kubernetes 1.32, you can also specify resource requests and limits at
+Provided your cluster has the `PodLevelResources`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled,
+you can specify resource requests and limits at
 the Pod level. At Pod level, Kubernetes {{< skew currentVersion >}}
 only supports resource requests or limits for specific resource types: `cpu` and /
-or `memory`. This feature is currently in alpha and with the feature enabled,
-Kubernetes allows you to declare an overall resource budget for the Pod, which is
-especially helpful when dealing with a large number of containers where it can be
-difficult to accurately gauge individual resource needs. Additionally, it enables
-containers within a Pod to share idle resources with each other, improving resource
-utilization.
--->
-从 Kubernetes 1.32 开始，你还可以在 Pod 级别指定资源请求和限制。
+or `memory` and / or `hugepages`. With this feature, Kubernetes allows you to declare an overall resource
+budget for the Pod, which is especially helpful when dealing with a large number of
+containers where it can be difficult to accurately gauge individual resource needs.
+Additionally, it enables containers within a Pod to share idle resources with each
+other, improving resource utilization.
+-->
+如果你的集群启用了 `PodLevelResources`
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)，
+你可以在 Pod 级别指定资源请求和限制。
 在 Pod 级别，Kubernetes {{< skew currentVersion >}} 仅支持为特定资源类型设置资源请求或限制：
-`cpu` 和/或 `memory`。此特性目前处于 Alpha 阶段。在启用该特性后，Kubernetes
-允许你声明 Pod 的总体资源预算，这在处理大量容器时特别有用，
-因为在这种情况下准确评估单个容器的资源需求可能会很困难。
+`cpu` 和/或 `memory` 和/或 `hugepages`。
+通过此特性，Kubernetes 允许你为 Pod 申领一个资源总预算，
+这在处理大量容器时特别有用，因为在这种情况下很难准确评估各个容器的资源需求。
 此外，它还允许 Pod 内的容器之间共享空闲资源，从而提高资源利用率。
 
 <!--
@@ -235,8 +238,10 @@ For a Pod, you can specify resource limits and requests for CPU and memory by in
 
 * `spec.resources.limits.cpu`
 * `spec.resources.limits.memory`
+* `spec.resources.limits.hugepages-<size>`
 * `spec.resources.requests.cpu`
 * `spec.resources.requests.memory`
+* `spec.resources.requests.hugepages-<size>`
 
 <!--
 ## Resource units in Kubernetes
@@ -1278,6 +1283,21 @@ extender.
 }
 ```
 
+<!--
+#### Extended resources allocation by DRA
+
+Extended resources allocation by DRA allows cluster administrators to specify an `extendedResourceName`
+in DeviceClass, then the devices matching the DeviceClass can be requested from a pod's extended
+resource requests. Read more about
+[Extended Resource allocation by DRA](/docs/concepts/scheduling-eviction/dynamic-resource-allocation/#extended-resource).
+-->
+#### DRA 扩展资源分配
+
+DRA 扩展资源分配允许集群管理员在 DeviceClass 中指定一个
+`extendedResourceName`，然后与所指定 DeviceClass 匹配的设备可以使用
+Pod 的扩展资源请求来获取。
+进一步阅读关于[使用 DRA 进行扩展资源分配](/zh-cn/docs/concepts/scheduling-eviction/dynamic-resource-allocation/#extended-resource)的内容。
+
 <!--
 ### Consuming extended resources
 
@@ -1606,6 +1626,7 @@ memory limit (and possibly request) for that container.
 * Read about [project quotas](https://www.linux.org/docs/man8/xfs_quota.html) in XFS
 * Read more about the [kube-scheduler configuration reference (v1)](/docs/reference/config-api/kube-scheduler-config.v1/)
 * Read more about [Quality of Service classes for Pods](/docs/concepts/workloads/pods/pod-qos/)
+* Read more about [Extended Resource allocation by DRA](/docs/concepts/scheduling-eviction/dynamic-resource-allocation/#extended-resource)
 -->
 * 获取[分配内存资源给容器和 Pod](/zh-cn/docs/tasks/configure-pod-container/assign-memory-resource/) 的实践经验
 * 获取[分配 CPU 资源给容器和 Pod](/zh-cn/docs/tasks/configure-pod-container/assign-cpu-resource/) 的实践经验
@@ -1614,3 +1635,4 @@ memory limit (and possibly request) for that container.
 * 阅读 XFS 中[项目配额](https://www.linux.org/docs/man8/xfs_quota.html)的文档
 * 进一步阅读 [kube-scheduler 配置参考（v1）](/zh-cn/docs/reference/config-api/kube-scheduler-config.v1/)
 * 进一步阅读 [Pod 的服务质量等级](/zh-cn/docs/concepts/workloads/pods/pod-qos/)
+* 进一步阅读[使用 DRA 进行扩展资源分配](/zh-cn/docs/concepts/scheduling-eviction/dynamic-resource-allocation/#extended-resource)

content/zh-cn/docs/concepts/scheduling-eviction/assign-pod-node.md

@@ -290,7 +290,8 @@ types, then the Pod can be scheduled onto a node if one of the specified terms
 can be satisfied (terms are ORed).
 -->
 如果你在与 nodeAffinity 类型关联的 nodeSelectorTerms 中指定多个条件，
-只要其中一个 `nodeSelectorTerms` 满足（各个条件按逻辑或操作组合）的话，Pod 就可以被调度到节点上。
+只要其中一个 `nodeSelectorTerms` 满足（各个条件按逻辑或操作组合）的话，
+Pod 就可以被调度到节点上。
 
 <!--
 If you specify multiple expressions in a single `matchExpressions` field associated with a
@@ -1150,6 +1151,44 @@ The above Pod will only run on the node `kube-01`.
 -->
 上面的 Pod 只能运行在节点 `kube-01` 之上。
 
+## nominatedNodeName
+
+{{< feature-state feature_gate_name="NominatedNodeNameForExpectation" >}}
+
+<!--
+`nominatedNodeName` can be used for external components to nominate node for a pending pod.
+This nomination is best effort: it might be ignored if the scheduler determines the pod cannot go to a nominated node.
+-->
+外部组件可以使用 `nominatedNodeName` 为待处理的 Pod 提名节点。
+这种提名是尽力而为的：如果调度器确定 Pod 不能进入被提名的节点，
+那么这个提名可能会被忽略。
+
+<!--
+Also, this field can be (over)written by the scheduler:
+- If the scheduler finds a node to nominate via the preemption.
+- If the scheduler decides where the pod is going, and move it to the binding cycle.
+  - Note that, in this case, `nominatedNodeName` is put only when the pod has to go through `WaitOnPermit` or `PreBind` extension points.
+
+Here is an example of a Pod status using the `nominatedNodeName` field:
+-->
+此外，此字段可以由调度器（重新）写入：
+- 如果调度器通过抢占找到一个可提名的节点。
+- 如果调度器决定了 Pod 的去向，并将其移至绑定阶段。
+  - 注意，在这种情况下，仅当 Pod 必须经过 `WaitOnPermit` 或
+    `PreBind` 扩展点时，才会设置 `nominatedNodeName`。
+
+以下是使用 `nominatedNodeName` 字段的 Pod 状态示例：
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: nginx
+...
+status:
+  nominatedNodeName: kube-01
+```
+
 <!--
 ## Pod topology spread constraints
 

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

@@ -141,7 +141,7 @@ Pod。实现 PreEnqueue、PreFilter、Filter、Reserve 或 Permit 的插件应
 
 ### QueueingHint
 
-{{< feature-state for_k8s_version="v1.32" state="beta" >}}
+{{< feature-state feature_gate_name="SchedulerQueueingHints" >}}
 
 <!--
 QueueingHint is a callback function for deciding whether a Pod can be requeued to the active queue or backoff queue.
@@ -155,17 +155,6 @@ QueueingHint 作为一个回调函数，用于决定是否将 Pod 重新排队
 当 QueueingHint 发现事件可能使 Pod 可调度时，Pod 将被放入活跃队列或回退队列，
 以便调度器可以重新尝试调度 Pod。
 
-{{< note >}}
-<!--
-In Kubernetes {{< skew currentVersion >}}, this feature gate is enabled by default,
-and you can disable it via the
-`SchedulerQueueingHints` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
--->
-在 Kubernetes 的 {{< skew currentVersion >}} 版本中，此特性门控默认启用，
-你可以通过 `SchedulerQueueingHints`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来禁用它。
-{{< /note >}}
-
 <!--
 ### QueueSort {#queue-sort}
 -->