Merge pull request #47862 from sabrinajess/CNV17623

CNV-17623: Note about NMO deployment change

Author: sjhala-ccs

modules/virt-about-node-maintenance.adoc

@@ -7,6 +7,11 @@
 
 Nodes can be placed into maintenance mode using the `oc adm` utility, or using `NodeMaintenance` custom resources (CRs).
 
+[NOTE]
+====
+The `node-maintenance-operator` (NMO) is no longer shipped with {VirtProductName}. It is now available to deploy as a standalone Operator from the *OperatorHub* in the {product-title} web console, or by using the OpenShift CLI (`oc`).
+====
+
 Placing a node into maintenance marks the node as unschedulable and drains all the virtual machines and pods from it. Virtual machine instances that have a `LiveMigrate` eviction strategy are live migrated to another node without loss of service. This eviction strategy is configured by default in virtual machine created from common templates but must be configured manually for custom virtual machines.
 
 Virtual machine instances without an eviction strategy are shut down. Virtual machines with a `RunStrategy` of `Running` or `RerunOnFailure` are recreated on another node. Virtual machines with a `RunStrategy` of `Manual` are not automatically restarted.

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

@@ -11,6 +11,7 @@ include::modules/virt-maintaining-bare-metal-nodes.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources:
 
+* xref:../../nodes/nodes/eco-node-maintenance-operator.adoc#installing-maintenance-operator-using-cli_node-maintenance-operator[Installing the Node Maintenance Operator by using the CLI]
 * 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]