Update articles/operator-nexus/howto-baremetal-functions.md

eak13 · web-flow · commit c8ac7c3db12b · 2024-04-24T13:10:53.000-05:00
diff --git a/articles/operator-nexus/howto-baremetal-functions.md b/articles/operator-nexus/howto-baremetal-functions.md
@@ -26,7 +26,7 @@ This article describes how to perform lifecycle management operations on Bare Me
 - **Replace the BMM**
 
 > [!IMPORTANT]
-> Disruptive command requests against a Kubernetes Control Plane (KCP) node are rejected if there is another disruptive action command already running against another KCP node or the full KCP is not available. This check is done to maintain the integrity of the Nexus instance and ensure multiple KCP nodes don't go down at once due to simultaneous disruptive actions.
+> Disruptive command requests against a Kubernetes Control Plane (KCP) node are rejected if there is another disruptive action command already running against another KCP node or the full KCP is not available. This check is done to maintain the integrity of the Nexus instance and ensure multiple KCP nodes don't go down at once due to simultaneous disruptive actions. If multiple nodes go down, it will break healthy quorum threshold of Kubernetes Control Plane.
 >
 > The bolded actions in the above list are considered disruptive (Power off, Restart, Reimage, Replace). Cordon without evacuate is not considered disruptive. Cordon with evacuate is considered disruptive.
 >

Original file line number	Diff line number	Diff line change
`@@ -26,7 +26,7 @@ This article describes how to perform lifecycle management operations on Bare Me`
`26`	`26`	`- Replace the BMM`
`27`	`27`
`28`	`28`	`> [!IMPORTANT]`
`29`		`-> Disruptive command requests against a Kubernetes Control Plane (KCP) node are rejected if there is another disruptive action command already running against another KCP node or the full KCP is not available. This check is done to maintain the integrity of the Nexus instance and ensure multiple KCP nodes don't go down at once due to simultaneous disruptive actions.`
	`29`	`+> Disruptive command requests against a Kubernetes Control Plane (KCP) node are rejected if there is another disruptive action command already running against another KCP node or the full KCP is not available. This check is done to maintain the integrity of the Nexus instance and ensure multiple KCP nodes don't go down at once due to simultaneous disruptive actions. If multiple nodes go down, it will break healthy quorum threshold of Kubernetes Control Plane.`
`30`	`30`	`>`
`31`	`31`	`> The bolded actions in the above list are considered disruptive (Power off, Restart, Reimage, Replace). Cordon without evacuate is not considered disruptive. Cordon with evacuate is considered disruptive.`
`32`	`32`	`>`