Merge pull request #47729 from carlory/fg-NodeOutOfServiceVolumeDetach

mark feature-gate NodeOutOfServiceVolumeDetach as removed

Author: k8s-ci-robot

content/en/docs/concepts/cluster-administration/node-shutdown.md

@@ -217,9 +217,7 @@ these pods will be stuck in terminating status on the shutdown node forever.
 
 To mitigate the above situation, a user can manually add the taint `node.kubernetes.io/out-of-service`
 with either `NoExecute` or `NoSchedule` effect to a Node marking it out-of-service.
-If the `NodeOutOfServiceVolumeDetach`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-is enabled on {{< glossary_tooltip text="kube-controller-manager" term_id="kube-controller-manager" >}},
-and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted
+If a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted
 if there are no matching tolerations on it and volume detach operations for the pods terminating on
 the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly
 on a different node.

content/en/docs/concepts/workloads/pods/pod-lifecycle.md

@@ -665,8 +665,7 @@ Additionally, PodGC cleans up any Pods which satisfy any of the following condit
 1. are orphan Pods - bound to a node which no longer exists,
 1. are unscheduled terminating Pods,
 1. are terminating Pods, bound to a non-ready node tainted with
-   [`node.kubernetes.io/out-of-service`](/docs/reference/labels-annotations-taints/#node-kubernetes-io-out-of-service),
-   when the `NodeOutOfServiceVolumeDetach` feature gate is enabled.
+   [`node.kubernetes.io/out-of-service`](/docs/reference/labels-annotations-taints/#node-kubernetes-io-out-of-service).
 
 Along with cleaning up the Pods, PodGC will also mark them as failed if they are in a non-terminal
 phase. Also, PodGC adds a Pod disruption condition when cleaning up an orphan Pod.

content/en/docs/reference/command-line-tools-reference/feature-gates/node-out-of-service-volume-detach.md

@@ -17,6 +17,9 @@ stages:
   - stage: stable
     defaultValue: true
     fromVersion: "1.28"  
+    toVersion: "1.31"
+
+removed: true
 ---
 When a Node is marked out-of-service using the
 `node.kubernetes.io/out-of-service` taint, Pods on the node will be forcefully deleted

content/en/docs/reference/labels-annotations-taints/_index.md

@@ -1591,10 +1591,8 @@ Example: `node.kubernetes.io/out-of-service:NoExecute`
 Used on: Node
 
 A user can manually add the taint to a Node marking it out-of-service.
-If the `NodeOutOfServiceVolumeDetach`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-is enabled on `kube-controller-manager`, and a Node is marked out-of-service with this taint,
-the Pods on the node will be forcefully deleted if there are no matching tolerations on it and
+If a Node is marked out-of-service with this taint, the Pods on the node 
+will be forcefully deleted if there are no matching tolerations on it and
 volume detach operations for the Pods terminating on the node will happen immediately.
 This allows the Pods on the out-of-service node to recover quickly on a different node.