CNV-45771: Added instructions to remove custom machine config pool

Author: Shikha Jhala

modules/virt-configuring-cluster-dpdk.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/vm_networking/virt-connecting-vm-to-sriov.adoc
+// * virt/vm_networking/virt-using-dpdk-with-sriov.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="virt-configuring-cluster-dpdk_{context}"]
@@ -17,7 +17,9 @@ You can configure an {product-title} cluster to run Data Plane Development Kit (
 .Procedure
 // Cannot label nodes in ROSA/OSD, but can edit machine pools
 . Map your compute nodes topology to determine which Non-Uniform Memory Access (NUMA) CPUs are isolated for DPDK applications and which ones are reserved for the operating system (OS).
-. Label a subset of the compute nodes with a custom role; for example, `worker-dpdk`:
+. If your {product-title} cluster uses separate control plane and compute nodes for high-availability:
+
+.. Label a subset of the compute nodes with a custom role; for example, `worker-dpdk`:
 +
 ifndef::openshift-rosa[]
 [source,terminal]
@@ -33,7 +35,7 @@ $ rosa edit machinepool --cluster=<cluster_name> <machinepool_ID> node-role.kube
 ----
 endif::openshift-rosa[]
 
-. Create a new `MachineConfigPool` manifest that contains the `worker-dpdk` label in the `spec.machineConfigSelector` object:
+.. Create a new `MachineConfigPool` manifest that contains the `worker-dpdk` label in the `spec.machineConfigSelector` object:
 +
 .Example `MachineConfigPool` manifest
 [source,yaml]

modules/virt-removing-custom-mcp.adoc

@@ -0,0 +1,30 @@
+// Module included in the following assemblies:
+//
+// * virt/vm_networking/virt-using-dpdk-with-sriov.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="virt-removing-custom-mcp_{context}"]
+= Removing a custom machine config pool for high-availability clusters
+
+You can delete a custom machine config pool that you previously created for your high-availability cluster.
+
+.Prerequisites
+* You have access to the cluster as a user with `cluster-admin` permissions.
+* You have installed the OpenShift CLI (`oc`).
+* You have created a custom machine config pool by labeling a subset of the compute nodes with a custom role and creating a `MachineConfigPool` manifest with that label.
+
+.Procedure
+
+. Remove the `worker-dpdk` label from the compute nodes by running the following command:
++
+[source,terminal]
+----
+$ oc label node <node_name> node-role.kubernetes.io/worker-dpdk-
+----
+
+. Delete the `MachineConfigPool` manifest that contains the `worker-dpdk` label by entering the following command:
++
+[source,terminal]
+----
+$ oc delete mcp worker-dpdk
+----

virt/vm_networking/virt-using-dpdk-with-sriov.adoc

@@ -24,6 +24,8 @@ ifndef::openshift-rosa,openshift-dedicated[]
 * link:https://access.redhat.com/solutions/5688941[Creating a custom machine config pool]
 endif::openshift-rosa,openshift-dedicated[]
 
+include::modules/virt-removing-custom-mcp.adoc[leveloffset=+2]
+
 include::modules/virt-configuring-vm-project-dpdk.adoc[leveloffset=+1]
 
 [role="_additional-resources_configuring-project-dpdk"]