Merge pull request #300750 from eak13/main

Reverting to pull Auto remediation text

Author: prmerger-automator[bot]

articles/operator-nexus/concepts-rack-resiliency.md

@@ -2,7 +2,7 @@
 title: Operator Nexus rack resiliency
 description: Document how rack resiliency works in Operator Nexus Near Edge
 ms.topic: article
-ms.date: 05/28/2025
+ms.date: 06/03/2025
 author: eak13
 ms.author: ekarandjeff
 ms.service: azure-operator-nexus
@@ -65,24 +65,6 @@ Operator Nexus supports control plane resiliency in single rack configurations b
 
 In disaster situations when the control plane loses quorum, there are impacts to the Kubernetes API across the instance. This scenario can affect a workload's ability to read and write Custom Resources (CRs) and talk across racks.
 
-## Automated remediation for Kubernetes Control Plane, Management Plane, and Compute nodes
-
-To avoid losing Kubernetes control plane (KCP) quorum, Operator Nexus provides automated remediation when certain server issues are detected. In certain situations, this automated remediation extends to Management Plane & Compute nodes as well.
-
-As a general overview of server resilience, here are the triggers for automated remediation:
-
-- For all servers: if a server fails to provision successfully after four hours, automated remediation occurs.
-- For all servers: if a running node is stuck in a read only root filesystem mode for 10 minutes, automated remediation occurs.
-- For KCP and Management Plane servers, if a Kubernetes node is in an Unknown state for 30 minutes, automated remediation occurs.
-
-Remediation Process:
-
-- Remediation of a Compute node is one reprovisioning attempt. If the reprovisioning fails, the node is marked `Unhealthy`.
-- Remediation of a Management Plane node is to attempt one reboot and then one reprovisioning attempt. If those steps fail, the node is marked `Unhealthy`.
-- Remediation of a KCP node is to attempt one reboot. If the reboot fails, the node is marked `Unhealthy` which triggers the immediate provisioning of the spare KCP node.
-
-Ongoing control plane resiliency requires a spare KCP node. When KCP node fails remediation and is marked `Unhealthy`, a deprovisioning of the node occurs, and an exchange with a suitable healthy Management Plane server occurs. This Management Plane server becomes the new spare KCP node. The failed KCP node is updated and labeled as a Management Plane node. Once the label changes, an attempt to provision the newly labeled management plane node occurs. If it fails to provision, the management plane remediation process takes over. If it fails provisioning or doesn't run successfully, the machine's status remains unhealthy and the user must fix. The unhealthy condition surfaces to the Bare Metal Machine's (BMM) `detailedStatus` fields in Azure, and clears through a BMM Replace action.
-
 ## Related Links
 
 [Determining Control Plane Role](./reference-near-edge-baremetal-machine-roles.md)