kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #51234 from arvinep/patch-2 

Fix some typos
pull/51237/head^2
Kubernetes Prow Robot 2025-06-11 07:46:56 -07:00 committed by GitHub
parent e542e8f81a eeb36c7a10
commit 61e622f3a4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/docs/concepts/workloads/controllers/deployment.md
View File

@ -1202,7 +1202,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%.
For example, when this value is set to 30%, the new ReplicaSet can be scaled up immediately when the
@ -1331,7 +1331,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/)

2
content/en/docs/concepts/workloads/controllers/replicaset.md
View File

@ -323,7 +323,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/)