Merge pull request #100592 from openshift-cherrypick-robot/cherry-pick-99902-to-enterprise-4.20

[enterprise-4.20] TELCODOCS-2039: Adding LACP status feature

Author: slovern

_topic_maps/_topic_map.yml

@@ -1593,6 +1593,8 @@ Topics:
     File: using-sriov-multicast
   - Name: Using DPDK and RDMA
     File: using-dpdk-and-rdma
+  - Name: High availability for pod-level bonds on SR-IOV networks
+    File: configure-lacp-for-sriov
   - Name: Using pod-level bonding for secondary networks
     File: using-pod-level-bonding
   - Name: Configuring hardware offloading

modules/installing-pfsr-operator-cli.adoc

@@ -0,0 +1,75 @@
+:_mod-docs-content-type: PROCEDURE
+[id="installing-pfsr-cli_{context}"]
+= Installing the PF Status Relay Operator using the CLI
+
+Install the PF Status Relay Operator to enable {product-title} to use Link Aggregation Control Protocol (LACP) as an active health check on physical functions (PFs). 
+
+.Prerequisites
+
+* You configured LACP on your upstream switch.
+
+* You configured pod-level bonding for your SR-IOV networks.
+
+* You installed the OpenShift CLI (`oc`).
+
+* You have cluster-admin privileges.
+
+.Procedure
+
+. Create the `openshift-pf-status-relay-operator` namespace by entering the following command:
++
+[source,bash]
+----
+$ cat << EOF| oc create -f -
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: openshift-pf-status-relay-operator
+  annotations:
+    workload.openshift.io/allowed: management
+EOF
+----
+
+. Create an `OperatorGroup` custom resource (CR) by entering the following command:
++
+[source,bash]
+----
+$ cat << EOF| oc create -f -
+apiVersion: operators.coreos.com/v1
+kind: OperatorGroup
+metadata:
+  name: pf-status-relay-operators
+  namespace: openshift-pf-status-relay-operator
+spec:
+  targetNamespaces:
+  - openshift-pf-status-relay-operator
+EOF
+----
+
+. Create a `Subscription` CR for the  PF Status Relay Operator by entering the following command:
++
+[source,bash]
+----
+$ cat << EOF| oc create -f -
+apiVersion: operators.coreos.com/v1alpha1
+kind: Subscription
+metadata:
+  name: pf-status-relay-operator-subscription
+  namespace: openshift-pf-status-relay-operator
+spec:
+  channel: stable
+  name: pf-status-relay-operator
+  source: redhat-operators
+  sourceNamespace: openshift-marketplace
+EOF
+----
+
+
+.Verification
+
+* To verify that the Operator is installed, enter the following command and then check that output shows `Succeeded` for the Operator:
++
+[source,bash]
+----
+$ oc get csv -n openshift-pf-status-relay-operator -o custom-columns=Name:.metadata.name,Phase:.status.phase
+----

modules/installing-pfsr-operator-console.adoc

@@ -0,0 +1,29 @@
+:_mod-docs-content-type: PROCEDURE
+[id="installing-pfsr-console_{context}"]
+= Installing the PF Status Relay Operator using the web console
+
+Install the PF Status Relay Operator to enable {product-title} to use Link Aggregation Control Protocol (LACP) as an active health check on physical functions (PFs).
+
+.Prerequisites
+
+* You configured LACP on your upstream switch.
+
+* You configured pod-level bonding for your SR-IOV networks.
+
+* You have cluster-admin privileges.
+
+.Procedure
+
+. Install the PF Status Relay Operator:
+
+.. In the {product-title} web console, click *Ecosystem* -> *Software Catalog*.
+
+.. Select *PF Status Relay Operator* from the list of available Operators, and then click *Install*.
+
+.. On the *Install Operator* page, under *Installed Namespace*, select *Operator recommended Namespace*.
+
+.. Click *Install*.
+
+.Verification 
+
+* Verify that the PF Status Relay Operator shows the *Status* as *Succeeded* on the Installed Operators dashboard.