[zh-cn] sync job replicaset downward-api

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

Author: my-git9

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

@@ -598,28 +598,39 @@ Pod 考虑在内，评估相关 Job 的 `.backoffLimit` 和 `.podFailurePolicy`
 There are situations where you want to fail a Job after some amount of retries
 due to a logical error in configuration etc.
 To do so, set `.spec.backoffLimit` to specify the number of retries before
-considering a Job as failed. The back-off limit is set by default to 6. Failed
-Pods associated with the Job are recreated by the Job controller with an
-exponential back-off delay (10s, 20s, 40s ...) capped at six minutes.
-
-The number of retries is calculated in two ways:
+considering a Job as failed.
 
-- The number of Pods with `.status.phase = "Failed"`.
-- When using `restartPolicy = "OnFailure"`, the number of retries in all the
- containers of Pods with `.status.phase` equal to `Pending` or `Running`.
+The `.spec.backoffLimit` is set by default to 6, unless the
+[backoff limit per index](#backoff-limit-per-index) (only Indexed Job) is specified.
+When `.spec.backoffLimitPerIndex` is specified, then `.spec.backoffLimit` defaults
+to 2147483647 (MaxInt32).
 
-If either of the calculations reaches the `.spec.backoffLimit`, the Job is
-considered failed.
+Failed Pods associated with the Job are recreated by the Job controller with an
+exponential back-off delay (10s, 20s, 40s ...) capped at six minutes.
 -->
 ### Pod 回退失效策略 {#pod-backoff-failure-policy}
 
 在有些情形下，你可能希望 Job 在经历若干次重试之后直接进入失败状态，
 因为这很可能意味着遇到了配置错误。
 为了实现这点，可以将 `.spec.backoffLimit` 设置为视 Job 为失败之前的重试次数。
-失效回退的限制值默认为 6。
+`.spec.backoffLimit` 的值默认为 6，
+除非指定了[每个索引的退避限制](#backoff-limit-per-index)（仅限带索引的 Job）。
+当指定 `.spec.backoffLimitPerIndex` 时，`.spec.backoffLimit`
+默认为 2147483647 (MaxInt32)。
+
 与 Job 相关的失效的 Pod 会被 Job 控制器重建，回退重试时间将会按指数增长
 （从 10 秒、20 秒到 40 秒）最多至 6 分钟。
 
+<!--
+The number of retries is calculated in two ways:
+
+- The number of Pods with `.status.phase = "Failed"`.
+- When using `restartPolicy = "OnFailure"`, the number of retries in all the
+ containers of Pods with `.status.phase` equal to `Pending` or `Running`.
+
+If either of the calculations reaches the `.spec.backoffLimit`, the Job is
+considered failed.
+-->
 计算重试次数有以下两种方法：
 - 计算 `.status.phase = "Failed"` 的 Pod 数量。
 - 当 Pod 的 `restartPolicy = "OnFailure"` 时，针对 `.status.phase` 等于 `Pending` 或
@@ -647,18 +658,7 @@ from failed Jobs is not lost inadvertently.
 -->
 ### 逐索引的回退限制 {#backoff-limit-per-index}
 
-{{< feature-state for_k8s_version="v1.29" state="beta" >}}
-
-{{< note >}}
-<!--
-You can only configure the backoff limit per index for an [Indexed](#completion-mode) Job, if you
-have the `JobBackoffLimitPerIndex` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-enabled in your cluster.
--->
-只有在集群中启用了 `JobBackoffLimitPerIndex`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)，
-才能为 [Indexed](#completion-mode) Job 配置逐索引的回退限制。
-{{< /note >}}
+{{< feature-state feature_gate_name="JobBackoffLimitPerIndex" >}}
 
 <!--
 When you run an [indexed](#completion-mode) Job, you can choose to handle retries
@@ -964,19 +964,6 @@ For more details, see [Job termination and cleanup](#job-termination-and-cleanup
 -->
 ## 成功策略 {#success-policy}
 
-{{< feature-state feature_gate_name="JobSuccessPolicy" >}}
-
-{{< note >}}
-<!--
-You can only configure a success policy for an Indexed Job if you have the
-`JobSuccessPolicy` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-enabled in your cluster.
--->
-只有你在集群中启用了 `JobSuccessPolicy`
-[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)时，
-才可以为带索引的 Job 配置成功策略。
-{{< /note >}}
-
 <!--
 When creating an Indexed Job, you can define when a Job can be declared as succeeded using a `.spec.successPolicy`,
 based on the pods that succeeded.

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

@@ -3,13 +3,6 @@ title: ReplicaSet
 api_metadata:
 - apiVersion: "apps/v1"
  kind: "ReplicaSet"
-feature:
- title: 自我修复
- anchor: ReplicationController 如何工作
- description: >
- 重新启动失败的容器，在节点死亡时替换并重新调度容器，
- 杀死不响应用户定义的健康检查的容器，
- 并且在它们准备好服务之前不会将它们公布给客户端。
 content_type: concept
 description: >-
  ReplicaSet 的作用是维持在任何给定时间运行的一组稳定的副本 Pod。
@@ -18,6 +11,12 @@ weight: 20
 hide_summary: true # 在章节索引中单独列出
 ---
 <!--
+# NOTE TO LOCALIZATION TEAMS
+#
+# If updating front matter for your localization because there is still
+# a "feature" key in this page, then you also need to update
+# content/??/docs/concepts/architecture/self-healing.md (which is where
+# it moved to)
 reviewers:
 - Kashomon
 - bprashanth
@@ -26,13 +25,6 @@ title: ReplicaSet
 api_metadata:
 - apiVersion: "apps/v1"
  kind: "ReplicaSet"
-feature:
- title: Self-healing
- anchor: How a ReplicaSet works
- description: >
- Restarts containers that fail, replaces and reschedules containers when nodes die,
- kills containers that don't respond to your user-defined health check,
- and doesn't advertise them to clients until they are ready to serve.
 content_type: concept
 description: >-
  A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time.
@@ -47,7 +39,6 @@ hide_summary: true # Listed separately in section index
 A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time. As such, it is often
 used to guarantee the availability of a specified number of identical Pods.
 -->
-
 ReplicaSet 的目的是维护一组在任何时候都处于运行状态的 Pod 副本的稳定集合。
 因此，它通常用来保证给定数量的、完全相同的 Pod 的可用性。
 

content/zh-cn/docs/concepts/workloads/pods/downward-api.md

@@ -202,6 +202,25 @@ for resources such as CPU and memory.
 -->
 ### 可通过 `resourceFieldRef` 获得的信息 {#downwardapi-resourceFieldRef}
 
+这些容器级别的字段允许你提供关于
+[请求和限制](/zh-cn/docs/concepts/configuration/manage-resources-containers/#requests-and-limits)
+的资源（如 CPU 和内存）信息。
+
+{{< note >}}
+{{< feature-state feature_gate_name="InPlacePodVerticalScaling" >}}
+<!--
+Container CPU and memory resources can be resized while the container is running.
+If this happens, a downward API volume will be updated,
+but environment variables will not be updated unless the container restarts.
+See [Resize CPU and Memory Resources assigned to Containers](/docs/tasks/configure-pod-container/resize-container-resources/)
+for more details.
+-->
+容器的 CPU 和内存资源可以在容器运行时调整大小。
+如果发生这种情况，Downward API 卷将会被更新，
+但是环境变量不会被更新，除非容器重启。
+更多详情请参见[调整分配给容器的 CPU 和内存资源](/zh-cn/docs/tasks/configure-pod-container/resize-container-resources/)。
+{{< /note >}}
+
 <!--
 `resource: limits.cpu`
 : A container's CPU limit
@@ -273,7 +292,6 @@ calculation.
 [节点可分配资源](/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable)
 计算并暴露 CPU 和内存的最大可分配值。
 
-
 ## {{% heading "whatsnext" %}}
 
 <!--