1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/installing-pfsr-operator-cli.adoc
2025-10-15 20:44:14 +00:00

76 lines
1.9 KiB
Plaintext

:_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
----