Merge pull request #57953 from ogradyp/TELCODOCS-1175

TELCODOCS-1175: Remove remediation content from docs.openshift.com

Author: kelbrown20

_topic_maps/_topic_map.yml

@@ -2296,19 +2296,8 @@ Topics:
     File: nodes-nodes-managing-max-pods
   - Name: Using the Node Tuning Operator
     File: nodes-node-tuning-operator
-  - Name: Remediation, fencing, and maintenance
-    Dir: ecosystems
-    Topics:
-    - Name: About node remediation, fencing, and maintentance
-      File: eco-about-remediation-fencing-maintenance
-    - Name: Using Self Node Remediation
-      File: eco-self-node-remediation-operator
-    - Name: Remediating nodes with Machine Health Checks
-      File: eco-machine-health-checks
-    - Name: Remediating nodes with Node Health Checks
-      File: eco-node-health-check-operator
-    - Name: Placing nodes in maintenance mode with Node Maintenance Operator
-      File: eco-node-maintenance-operator
+  - Name: Remediating, fencing, and maintaining nodes
+    File: nodes-remediating-fencing-maintaining-rhwa
   - Name: Understanding node rebooting
     File: nodes-nodes-rebooting
   - Name: Freeing node resources using garbage collection

nodes/nodes/nodes-remediating-fencing-maintaining-rhwa.adoc

@@ -0,0 +1,11 @@
+:_content-type: ASSEMBLY
+[id="nodes-remediating-fencing-maintaining-rhwa"]
+= Remediating, fencing, and maintaining nodes
+include::_attributes/common-attributes.adoc[]
+:context: nodes-remediating-fencing-maintaining-rhwa
+
+toc::[]
+
+When node-level failures occur, such as the kernel hangs or network interface controllers (NICs) fail, the work required from the cluster does not decrease, and workloads from affected nodes need to be restarted somewhere. Failures affecting these workloads risk data loss, corruption, or both. It is important to isolate the node, known as `fencing`, before initiating recovery of the workload, known as `remediation`, and recovery of the node.
+
+For more information on remediation, fencing, and maintaining nodes, see the link:https://access.redhat.com/documentation/en-us/workload_availability_for_red_hat_openshift/23.2/html-single/remediation_fencing_and_maintenance/index#about-remediation-fencing-maintenance[Workload Availability for Red Hat OpenShift] documentation.

virt/install/preparing-cluster-for-virt.adoc

@@ -78,7 +78,8 @@ You can configure one of the following high-availability (HA) options for your c
 In {product-title} clusters installed using installer-provisioned infrastructure and with MachineHealthCheck properly configured, if a node fails the MachineHealthCheck and becomes unavailable to the cluster, it is recycled. What happens next with VMs that ran on the failed node depends on a series of conditions. See xref:../../virt/virtual_machines/virt-create-vms.adoc#virt-about-runstrategies-vms_virt-create-vms[About RunStrategies for virtual machines] for more detailed information about the potential outcomes and how RunStrategies affect those outcomes.
 ====
 
-* Automatic high availability for both IPI and non-IPI is available by using the xref:../../nodes/nodes/ecosystems/eco-node-health-check-operator.adoc#node-health-check-operator[Node Health Check Operator] on the {product-title} cluster to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses the Self Node Remediation Operator to remediate the unhealthy nodes.
+* Automatic high availability for both IPI and non-IPI is available by using the *Node Health Check Operator* on the {product-title} cluster to deploy the `NodeHealthCheck` controller. The controller identifies unhealthy nodes and uses the Self Node Remediation Operator to remediate the unhealthy nodes. For more information on remediation, fencing, and maintaining nodes, see the link:https://access.redhat.com/documentation/en-us/workload_availability_for_red_hat_openshift/23.2/html-single/remediation_fencing_and_maintenance/index#about-remediation-fencing-maintenance[Workload Availability for Red Hat OpenShift] documentation.
+
 +
 --
 ifdef::openshift-enterprise[]

virt/node_maintenance/virt-about-node-maintenance.adoc

@@ -13,9 +13,9 @@ include::modules/virt-maintaining-bare-metal-nodes.adoc[leveloffset=+1]
 [role="_additional-resources"]
 [id="additional-resources_virt-about-node-maintenance"]
 == Additional resources
-* xref:../../nodes/nodes/ecosystems/eco-node-maintenance-operator.adoc#installing-maintenance-operator-using-cli_node-maintenance-operator[Installing the Node Maintenance Operator by using the CLI]
-* xref:../../nodes/nodes/ecosystems/eco-node-maintenance-operator.adoc#setting-node-in-maintenance-mode[Setting a node to maintenance mode]
-* xref:../../nodes/nodes/ecosystems/eco-node-maintenance-operator.adoc#resuming-node-from-maintenance-mode[Resuming a node from maintenance mode]
+* xref:../../nodes/nodes/nodes-remediating-fencing-maintaining-rhwa.adoc#nodes-remediating-fencing-maintaining-rhwa[Installing the Node Maintenance Operator by using the CLI]
+* xref:../../nodes/nodes/nodes-remediating-fencing-maintaining-rhwa.adoc#nodes-remediating-fencing-maintaining-rhwa[Setting a node to maintenance mode]
+* xref:../../nodes/nodes/nodes-remediating-fencing-maintaining-rhwa.adoc#nodes-remediating-fencing-maintaining-rhwa[Resuming a node from maintenance mode]
 * xref:../../virt/virtual_machines/virt-create-vms.adoc#virt-about-runstrategies-vms_virt-create-vms[About RunStrategies for virtual machines]
 * xref:../../virt/live_migration/virt-live-migration.adoc#virt-live-migration[Virtual machine live migration]
 * xref:../../virt/live_migration/virt-configuring-vmi-eviction-strategy.adoc#virt-configuring-vmi-eviction-strategy[Configuring virtual machine eviction strategy]

virt/upgrading-virt.adoc

@@ -10,7 +10,7 @@ Learn how Operator Lifecycle Manager (OLM) delivers z-stream and minor version u
 
 [NOTE]
 ====
-* The Node Maintenance Operator (NMO) is no longer shipped with {VirtProductName}. You can xref:../nodes/nodes/ecosystems/eco-node-maintenance-operator.adoc#node-maintenance-operator[install the NMO] from the *OperatorHub* in the {product-title} web console, or by using the OpenShift CLI (`oc`).
+* The Node Maintenance Operator (NMO) is no longer shipped with {VirtProductName}. You can *install the NMO* from the *OperatorHub* in the {product-title} web console, or by using the OpenShift CLI (`oc`). For more information on remediation, fencing, and maintaining nodes, see the link:https://access.redhat.com/documentation/en-us/workload_availability_for_red_hat_openshift/23.2/html-single/remediation_fencing_and_maintenance/index#about-remediation-fencing-maintenance[Workload Availability for Red Hat OpenShift] documentation.
 +
 You must perform one of the following tasks before updating to {VirtProductName} 4.11 from {VirtProductName} 4.10.2 and later releases: