Updates for Acrolinx

Author: Andrew

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/2024
+ms.date: 05/28/2025
 author: eak13
 ms.author: ekarandjeff
 ms.service: azure-operator-nexus
@@ -19,12 +19,15 @@ Operator Nexus ensures the availability of three active Kubernetes control plane
 > [!TIP]
 > The Kubernetes control plane is a set of components that manage the state of a Kubernetes cluster, schedule workloads, and respond to cluster events. It includes the API server, etcd storage, scheduler, and controller managers.
 >
-> The remaining management nodes contain various operators which run the platform software as well as other components performing support capabilities for monitoring, storage and networking.
+> The remaining management nodes contain various operators which run the platform software and other components performing support capabilities for monitoring, storage, and networking.
 
-During runtime upgrades, Operator Nexus implements a sequential upgrade of the control plane nodes, thereby preserving resiliency throughout the upgrade process.
+During runtime upgrades, Operator Nexus implements a sequential upgrade of the control plane nodes which preserves resiliency throughout the upgrade process.
 
 Three compute racks:
 
+KCP = Kubernetes Control Plane Node
+MGMT = Mangement Node Pool Node
+
 | Rack 1    | Rack 2 | Rack 3 |
 | --------- | ------ | ------ |
 | KCP       | KCP    | KCP    |
@@ -50,7 +53,7 @@ Two compute racks:
 
 Single compute rack:
 
-Operator Nexus supports control plane resiliency in single rack configurations by having three management nodes within the rack. For example, a single rack configuration with three management servers will provide an equivalent number of active control planes to ensure resiliency within a rack.
+Operator Nexus supports control plane resiliency in single rack configurations by having three management nodes within the rack. For example, a single rack configuration with three management servers provides an equivalent number of active control planes to ensure resiliency within a rack.
 
 | Rack 1 |
 | ------ |
@@ -62,23 +65,23 @@ 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
+## 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 Readonly Root Filesystem mode for ten minutes, 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 re-provisioning attempt. If the re-provisioning fails, the node is marked `Unhealthy`.
-- Remediation of a Management Plane node is to attempt one reboot and then one re-provisioning attempt. If those steps fail, the node is marked `Unhealthy`.
+- 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.
 
-A spare KCP node is required to ensure ongoing control plane resiliency. When KCP node fails remediation and is marked `Unhealthy`, it is deprovisioned and then swapped with a suitable healthy Management Plane host. This Management Plane host becomes the new spare KCP node. The failed KCP node is updated to be labeled as a Management Plane node. If it continues to fail to provision or run successfully, it is left in an unhealthy state for the customer to fix the underlying issue. The unhealthy condition is surfaced to the BMM detailedStatus in Azure, and it can be cleared by a BMM Replace action.
+A spare KCP node is required to ensure ongoing control plane resiliency. When KCP node fails remediation and is marked `Unhealthy`, it's deprovisioned and then swapped with a suitable healthy Management Plane host. This Management Plane host becomes the new spare KCP node. The failed KCP node is updated and labeled as a Management Plane node. If it continues to fail to provision or run successfully, it's left in an unhealthy state for the customer to fix the underlying issue. The unhealthy condition surfaces to the Bare Metal Machine's (BMM) `detailedStatus` fields in Azure, and clears through a BMM Replace action.
 
 ## Related Links