[zh-cn]sync storage-limits volumes

my-git9 · my-git9 · commit ae74fa0d3cc2 · 2025-04-24T21:22:43.000+08:00
Signed-off-by: xin.li &lt;xin.li@daocloud.io&gt;
diff --git a/content/zh-cn/docs/concepts/storage/storage-limits.md b/content/zh-cn/docs/concepts/storage/storage-limits.md
@@ -50,7 +50,7 @@ Kubernetes 调度器对挂接到一个节点的卷数有默认限制：
   <tr><td><a href="https://cloud.google.com/persistent-disk/">Google Persistent Disk</a></td><td>16</td></tr>
   <tr><td><a href="https://azure.microsoft.com/en-us/services/storage/main-disks/">Microsoft Azure Disk Storage</a></td><td>16</td></tr>
 </table>
- -->
+-->
 <table>
   <tr><th>云服务</th><th>每节点最大卷数</th></tr>
   <tr><td><a href="https://aws.amazon.com/ebs/">Amazon Elastic Block Store (EBS)</a></td><td>39</td></tr>
@@ -143,3 +143,62 @@ Refer to the [CSI specifications](https://github.com/container-storage-interface
   参考 [CSI 规范](https://github.com/container-storage-interface/spec/blob/master/spec.md#nodegetinfo)获取更多详细信息。
 
 * 对于由已迁移到 CSI 驱动的树内插件管理的卷，最大卷数将是 CSI 驱动报告的卷数。
+
+<!--
+### Mutable CSI Node Allocatable Count
+-->
+### 可变的 CSI 节点可分配数   {#mutable-csi-node-allocatable-count}
+
+{{< feature-state state="alpha" for_k8s_version="v1.33" >}}
+
+<!--
+CSI drivers can dynamically adjust the maximum number of volumes that can be attached to a Node at runtime. This enhances scheduling accuracy and reduces pod scheduling failures due to changes in resource availability.
+-->
+CSI 驱动可以在运行时动态调整可以挂载到 Node 的最大卷数量。
+这提高了调度准确性，并减少了由于资源可用性变化导致的 Pod 调度失败。
+
+<!--
+This is an alpha feature and is disabled by default.
+
+To use this feature, you must enable the `MutableCSINodeAllocatableCount` feature gate on the following components:
+-->
+这是一个 Alpha 级别特性，默认情况下是禁用的。
+
+要使用此特性，你必须在以下组件上启用 `MutableCSINodeAllocatableCount`
+特性门控：
+
+- `kube-apiserver`
+- `kubelet`
+
+<!--
+#### Periodic Updates
+
+When enabled, CSI drivers can request periodic updates to their volume limits by setting the `nodeAllocatableUpdatePeriodSeconds` field in the `CSIDriver` specification. For example:
+-->
+#### 定期更新
+
+当启用时，CSI 驱动可以通过在 `CSIDriver` 规约中设置
+`nodeAllocatableUpdatePeriodSeconds` 字段来请求定期更新其卷限制。
+例如：
+
+```yaml
+apiVersion: storage.k8s.io/v1
+kind: CSIDriver
+metadata:
+  name: hostpath.csi.k8s.io
+spec:
+  nodeAllocatableUpdatePeriodSeconds: 60
+```
+
+<!--
+Kubelet will periodically call the corresponding CSI driver’s `NodeGetInfo` endpoint to refresh the maximum number of attachable volumes, using the interval specified in `nodeAllocatableUpdatePeriodSeconds`. The minimum allowed value for this field is 10 seconds.
+-->
+kubelet 将使用 `nodeAllocatableUpdatePeriodSeconds`
+中指定的时间间隔，定期调用相应的 CSI 驱动的 `NodeGetInfo`
+端点来刷新可挂接卷的最大数量。此字段允许的最小值为 10 秒。
+
+<!--
+Additionally, if a volume attachment operation fails with a `ResourceExhausted` error (gRPC code 8), Kubernetes triggers an immediate update to the allocatable volume count for that Node.
+-->
+此外，如果卷挂接操作失败并返回 `ResourceExhausted` 错误（gRPC 代码 8），
+Kubernetes 会立即触发对该 Node 的可分配卷数量的更新。
diff --git a/content/zh-cn/docs/concepts/storage/volumes.md b/content/zh-cn/docs/concepts/storage/volumes.md
@@ -588,13 +588,13 @@ Kubernetes 项目建议你转为使用
 
 {{< warning >}}
 <!--
-The `gitRepo` volume type is deprecated.
+The `gitRepo` volume plugin is deprecated and is disabled by default.
 
 To provision a Pod that has a Git repository mounted, you can mount an
 [`emptyDir`](#emptydir) volume into an [init container](/docs/concepts/workloads/pods/init-containers/)
 that clones the repo using Git, then mount the [EmptyDir](#emptydir) into the Pod's container.
 -->
-`gitRepo` 卷类型已经被弃用。
+`gitRepo` 卷插件已经被弃用且默认禁用。
 
 如果需要制备已挂载 Git 仓库的 Pod，你可以将
 [EmptyDir](#emptydir) 卷挂载到 [Init 容器](/zh-cn/docs/concepts/workloads/pods/init-containers/)中，
@@ -618,6 +618,15 @@ part of a policy to reject use of `gitRepo` volumes:
 ```
 {{< /warning >}}
 
+<!--
+You can use this deprecated storage plugin in your cluster if you explicitly
+enable the `GitRepoVolumeDriver`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
+-->
+如果你明确启用 `GitRepoVolumeDriver`
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)，
+你可以在集群中使用这个已废弃的存储插件。
+
 <!--
 A `gitRepo` volume is an example of a volume plugin. This plugin
 mounts an empty directory and clones a git repository into this directory
@@ -1083,16 +1092,20 @@ OCI 对象将以只读方式被挂载到单个目录（`spec.containers[*].volum
 <!--
 Besides that:
 
-- Sub path mounts for containers are not supported
-  (`spec.containers[*].volumeMounts.subpath`).
+- [`subPath`](/docs/concepts/storage/volumes/#using-subpath) or
+  [`subPathExpr`](/docs/concepts/storage/volumes/#using-subpath-expanded-environment)
+  mounts for containers (`spec.containers[*].volumeMounts.[subPath,subPathExpr]`)
+  are only supported from Kubernetes v1.33.
 - The field `spec.securityContext.fsGroupChangePolicy` has no effect on this
   volume type.
 - The [`AlwaysPullImages` Admission Controller](/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages)
   does also work for this volume source like for container images.
 -->
 此外：
 
-- 不支持容器使用子路径挂载（`spec.containers[*].volumeMounts.subpath`）。
+- 从 Kubernetes v1.33 开始，才支持容器的 [`subPath`](/zh-cn/docs/concepts/storage/volumes/#using-subpath) 或
+  [`subPathExpr`](/zh-cn/docs/concepts/storage/volumes/#using-subpath-expanded-environment)
+  挂载（`spec.containers[*].volumeMounts.[subPath,subPathExpr]`）。
 - `spec.securityContext.fsGroupChangePolicy` 字段对这种卷没有效果。
 - [`AlwaysPullImages` 准入控制器](/zh-cn/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages)也适用于此卷源，
   就像适用于容器镜像一样。
@@ -1450,30 +1463,18 @@ For more details, see the
 -->
 #### Portworx CSI 迁移
 
-{{< feature-state for_k8s_version="v1.25" state="beta" >}}
+{{< feature-state feature_gate_name="CSIMigrationPortworx" >}}
 
 <!--
-By default, Kubernetes {{% skew currentVersion %}} attempts to migrate legacy
-Portworx volumes to use CSI. (CSI migration for Portworx has been available since
-Kubernetes v1.23, but was only turned on by default since the v1.31 release).
-If you want to disable automatic migration, you can set the `CSIMigrationPortworx`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-to `false`; you need to make that change for the kube-controller-manager **and** on
-every relevant kubelet.
-
-It redirects all plugin operations from the existing in-tree plugin to the
-`pxd.portworx.com` Container Storage Interface (CSI) Driver.
+In Kubernetes {{% skew currentVersion %}}, all operations for the in-tree
+Portworx volumes are redirected to the `pxd.portworx.com` 
+Container Storage Interface (CSI) Driver by default. 
 [Portworx CSI Driver](https://docs.portworx.com/portworx-enterprise/operations/operate-kubernetes/storage-operations/csi)
 must be installed on the cluster.
 -->
-默认情况下，Kubernetes {{% skew currentVersion %}} 尝试将传统的 Portworx 卷迁移为使用 CSI。
-（Portworx 的 CSI 迁移自 Kubernetes v1.23 版本以来一直可用，但从 v1.31 版本开始才默认启用）。
-如果你想禁用自动迁移，可以将 `CSIMigrationPortworx`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/) 设置为 `false`；
-你需要在 kube-controller-manager **和**每个相关的 kubelet 上进行此更改。
-
-它将所有插件操作不再指向树内插件（In-Tree Plugin），转而指向
-`pxd.portworx.com` 容器存储接口（Container Storage Interface，CSI）驱动。
+在 Kubernetes {{% skew currentVersion %}} 中，默认情况下，
+所有针对树内 Portworx 卷的操作都会被重定向到 
+`pxd.portworx.com` 容器存储接口（CSI）驱动。
 [Portworx CSI 驱动程序](https://docs.portworx.com/portworx-enterprise/operations/operate-kubernetes/storage-operations/csi)必须安装在集群上。
 
 <!--

Original file line number	Diff line number	Diff line change
`@@ -50,7 +50,7 @@ Kubernetes 调度器对挂接到一个节点的卷数有默认限制：`
`50`	`50`
Google Persistent Disk	16
`51`	`51`
Microsoft Azure Disk Storage	16
`52`	`52`