Merge pull request #51301 from asa3311/sync-zh-186

[zh] sync ntro deployment replicaset
pull/51325/head
Kubernetes Prow Robot 2025-06-20 18:18:52 -07:00 committed by GitHub
commit 4416cf7556
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 7 additions and 7 deletions

View File

@ -614,17 +614,17 @@ kernel patch.
<!--
### Mirantis Container Runtime {#mcr}
[Mirantis Container Runtime](https://docs.mirantis.com/mcr/20.10/overview.html) (MCR)
[Mirantis Container Runtime](https://docs.mirantis.com/mcr/25.0/overview.html) (MCR)
is available as a container runtime for all Windows Server 2019 and later versions.
See [Install MCR on Windows Servers](https://docs.mirantis.com/mcr/20.10/install/mcr-windows.html) for more information.
See [Install MCR on Windows Servers](https://docs.mirantis.com/mcr/25.0/install/mcr-windows.html) for more information.
-->
### Mirantis 容器运行时 {#mcr}
[Mirantis 容器运行时](https://docs.mirantis.com/mcr/20.10/overview.html)MCR
[Mirantis 容器运行时](https://docs.mirantis.com/mcr/25.0/overview.html)MCR
可作为所有 Windows Server 2019 和更高版本的容器运行时。
有关更多信息,请参考[在 Windows Server 上安装 MCR](https://docs.mirantis.com/mcr/20.10/install/mcr-windows.html)。
有关更多信息,请参考[在 Windows Server 上安装 MCR](https://docs.mirantis.com/mcr/25.0/install/mcr-windows.html)。
<!--
## Windows OS version compatibility {#windows-os-version-support}

View File

@ -2161,7 +2161,7 @@ at all times during the update is at least 70% of the desired Pods.
`.spec.strategy.rollingUpdate.maxSurge` is an optional field that specifies the maximum number of Pods
that can be created over the desired number of Pods. The value can be an absolute number (for example, 5) or a
percentage of desired Pods (for example, 10%). The value cannot be 0 if `MaxUnavailable` is 0. The absolute number
percentage of desired Pods (for example, 10%). The value cannot be 0 if `maxUnavailable` is 0. The absolute number
is calculated from the percentage by rounding up. The default value is 25%.
-->
##### 最大峰值 {#max-surge}
@ -2326,7 +2326,7 @@ a Pod is considered ready, see [Container Probes](/docs/concepts/workloads/pods/
{{< feature-state feature_gate_name="DeploymentReplicaSetTerminatingReplicas" >}}
You can enable this feature it by setting the `DeploymentReplicaSetTerminatingReplicas`
You can enable this feature 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/)

View File

@ -535,7 +535,7 @@ ReplicaSets do not support a rolling update directly.
{{< feature-state feature_gate_name="DeploymentReplicaSetTerminatingReplicas" >}}
You can enable this feature it by setting the `DeploymentReplicaSetTerminatingReplicas`
You can enable this feature 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/)