openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 15:46:57 +01:00
Code Issues Releases Activity

Follow-up edits to PR#29487

Browse Source
This commit is contained in:
Ashley Hardin
2021-02-15 10:58:46 -05:00
parent 580a666969
commit 84cc104f10
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
modules/cnf-installing-the-operators.adoc
View File

@@ -4,7 +4,7 @@
// *scalability_and_performance/cnf-provisioning-and-deploying-a-distributed-unit.adoc
[id="cnf-installing-the-operators_{context}"]
= Installing the operators
= Installing the Operators
[id="cnf-installing-the-performnce-addon-operator_{context}"]
== Installing the Performance Addon Operator
@@ -100,7 +100,7 @@ metadata:
EOF
----
. Apply the operator group:
. Apply the Operator group:
+
[source,yaml]
----
@@ -231,6 +231,7 @@ spec:
EOF
----
[id="cnf-installing-the-operators-verifying-your-changes_{context}"]
== Verifying your changes
Use the following command to verify the changes have been applied to the cluster:

2
modules/cnf-modifying-and-applying-the-default-profile.adoc
View File

@@ -11,7 +11,7 @@ You can apply the profile manually or with the toolset of your choice, such as A
[NOTE]
====
This procedure applies the DU profile step-by-step. If the profile is pulled together into a single project and applied in one step, issues will occur between the MCO and
the SRIOV operators if an Intel NIC is used for networking traffic. To avoid a race condition between the MCO and the SRIOV operators it is recommended that the DU application be applied in three steps:
the SRIOV operators if an Intel NIC is used for networking traffic. To avoid a race condition between the MCO and the SRIOV Operators, it is recommended that the DU application be applied in three steps:
. Apply the profile without SRIOV.
. Wait for the cluster to settle.