Merge pull request #54569 from slovern/TELCODOCS-982-SRO-REMOVAL

TELCODOCS-982 Replacing SRO with KMM

Author: mburke5678

_topic_maps/_topic_map.yml

@@ -582,8 +582,6 @@ Topics:
   Distros: openshift-enterprise
 - Name: Updating hardware on nodes running on vSphere
   File: updating-hardware-on-nodes-running-on-vsphere
-- Name: Updating a cluster that includes the Special Resource Operator
-  File: updating-clusters-sro
 # - Name: Troubleshooting an update
 #  File: updating-troubleshooting
 ---
@@ -2494,8 +2492,6 @@ Topics:
   File: about-hardware-enablement
 - Name: Driver Toolkit
   File: psap-driver-toolkit
-- Name: Special Resource Operator
-  File: psap-special-resource-operator
 - Name: Node Feature Discovery Operator
   File: psap-node-feature-discovery-operator
 ---

hardware_enablement/about-hardware-enablement.adoc

@@ -9,5 +9,4 @@ toc::[]
 Many applications require specialized hardware or software that depends on kernel modules or drivers. You can use driver containers to load out-of-tree kernel modules on {op-system-first} nodes. To deploy out-of-tree drivers during cluster installation, use the `kmods-via-containers` framework. To load drivers or kernel modules on an existing {product-title} cluster, {product-title} offers several tools:
 
 * The Driver Toolkit is a container image that is a part of every {product-title} release. It contains the kernel packages and other common dependencies that are needed to build a driver or kernel module. The Driver Toolkit can be used as a base image for driver container image builds on {product-title}.
-* The Special Resource Operator (SRO) orchestrates the building and management of driver containers to load kernel modules and drivers on an existing OpenShift or Kubernetes cluster.
 * The Node Feature Discovery (NFD) Operator adds node labels for CPU capabilities, kernel version, PCIe device vendor IDs, and more.