From 4d83be26c77a3a873f8d749e30112e2c5fedc339 Mon Sep 17 00:00:00 2001 From: Arvin Ebrahimpour <16176259+arvinep@users.noreply.github.com> Date: Wed, 11 Jun 2025 11:09:11 +0200 Subject: [PATCH 1/3] Fix a typo in deployment.md Removed the typo "it" in "You can enable this feature it by setting" --- content/en/docs/concepts/workloads/controllers/deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/deployment.md b/content/en/docs/concepts/workloads/controllers/deployment.md index 700d23954d..d19b8a92c3 100644 --- a/content/en/docs/concepts/workloads/controllers/deployment.md +++ b/content/en/docs/concepts/workloads/controllers/deployment.md @@ -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/) From c6f91061b7a8fde93c5373de19fd115fd8e57a5a Mon Sep 17 00:00:00 2001 From: Arvin Ebrahimpour <16176259+arvinep@users.noreply.github.com> Date: Wed, 11 Jun 2025 15:35:44 +0200 Subject: [PATCH 2/3] Update deployment.md --- content/en/docs/concepts/workloads/controllers/deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/deployment.md b/content/en/docs/concepts/workloads/controllers/deployment.md index d19b8a92c3..31458d6c43 100644 --- a/content/en/docs/concepts/workloads/controllers/deployment.md +++ b/content/en/docs/concepts/workloads/controllers/deployment.md @@ -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 From eeb36c7a1027f6b5fb6d33bfae6f228438001369 Mon Sep 17 00:00:00 2001 From: Arvin Ebrahimpour <16176259+arvinep@users.noreply.github.com> Date: Wed, 11 Jun 2025 15:37:37 +0200 Subject: [PATCH 3/3] Update replicaset.md --- content/en/docs/concepts/workloads/controllers/replicaset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/replicaset.md b/content/en/docs/concepts/workloads/controllers/replicaset.md index cc387928f7..21979417d6 100644 --- a/content/en/docs/concepts/workloads/controllers/replicaset.md +++ b/content/en/docs/concepts/workloads/controllers/replicaset.md @@ -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/)