-
Notifications
You must be signed in to change notification settings - Fork 1.8k
TELCODOCS-2039: Adding LACP status feature #99902
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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 | ||
| ---- |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is a problem here but I will fix it today and backport it to 4.20. I believe it is safe to leave this as it is