[zh-cn] sync replicaset.md and deployment.md

Author: Eason1118

content/zh-cn/docs/concepts/workloads/controllers/deployment.md

@@ -2321,6 +2321,32 @@ a Pod is considered ready, see [Container Probes](/docs/concepts/workloads/pods/
 要了解何时 Pod 被视为就绪，
 可参考[容器探针](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/#container-probes)。
 
+<!--
+### Terminating Pods
+
+{{< feature-state feature_gate_name="DeploymentReplicaSetTerminatingReplicas" >}}
+
+You can enable this feature it by setting the `DeploymentReplicaSetTerminatingReplicas`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/)
+and on the [kube-controller-manager](/docs/reference/command-line-tools-reference/kube-controller-manager/)
+Pods that become terminating due to deletion or scale down may take a long time to terminate, and may consume
+additional resources during that period. As a result, the total number of all pods can temporarily exceed
+`.spec.replicas`. Terminating pods can be tracked using the `.status.terminatingReplicas` field of the Deployment.
+-->
+### 终止 Pod  {#terminating-pods}
+
+{{< feature-state feature_gate_name="DeploymentReplicaSetTerminatingReplicas" >}}
+
+你可以通过在 [API 服务器](/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/)
+和 [kube-controller-manager](/zh-cn/docs/reference/command-line-tools-reference/kube-controller-manager/)
+上启用 `DeploymentReplicaSetTerminatingReplicas`
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来开启此功能。
+
+由于删除或缩减副本导致的终止中的 Pod 可能需要较长时间才能完成终止，且在此期间可能会消耗额外资源。
+因此，所有 Pod 的总数可能会暂时超过 `.spec.replicas` 指定的数量。
+可以通过 Deployment 的 `.status.terminatingReplicas` 字段来跟踪终止中的 Pod。
+
 <!--
 ### Revision History Limit
 

content/zh-cn/docs/concepts/workloads/controllers/replicaset.md

@@ -539,6 +539,33 @@ ReplicaSets do not support a rolling update directly.
 [Deployment](/zh-cn/docs/concepts/workloads/controllers/deployment/#creating-a-deployment)
 资源，因为 ReplicaSet 并不直接支持滚动更新。
 
+<!--
+### Terminating Pods
+
+{{< feature-state feature_gate_name="DeploymentReplicaSetTerminatingReplicas" >}}
+
+You can enable this feature it by setting the `DeploymentReplicaSetTerminatingReplicas`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/)
+and on the [kube-controller-manager](/docs/reference/command-line-tools-reference/kube-controller-manager/)
+
+Pods that become terminating due to deletion or scale down may take a long time to terminate, and may consume
+additional resources during that period. As a result, the total number of all pods can temporarily exceed
+`.spec.replicas`. Terminating pods can be tracked using the `.status.terminatingReplicas` field of the ReplicaSet.
+-->
+### 终止中的 Pod  {#terminating-pods}
+
+{{< feature-state feature_gate_name="DeploymentReplicaSetTerminatingReplicas" >}}
+
+你可以通过在 [API 服务器](/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/)
+和 [kube-controller-manager](/zh-cn/docs/reference/command-line-tools-reference/kube-controller-manager/)
+上启用 `DeploymentReplicaSetTerminatingReplicas`
+[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)来开启此功能。
+
+由于删除或缩减副本导致的终止中的 Pod 可能需要较长时间才能完成终止，且在此期间可能会消耗额外资源。
+因此，所有 Pod 的总数可能会暂时超过 `.spec.replicas` 指定的数量。
+可以通过 ReplicaSet 的 `.status.terminatingReplicas` 字段来跟踪终止中的 Pod。
+
 <!--
 ### Isolating Pods from a ReplicaSet