|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * networking/hardware_networks/configuring-sriov-operator.adoc |
| 4 | + |
| 5 | +:_content-type: PROCEDURE |
| 6 | +[id="sriov-operator-hosted-control-planes_{context}"] |
| 7 | += Deploying the SR-IOV Operator for hosted control planes |
| 8 | + |
| 9 | +:FeatureName: Hosted control planes |
| 10 | +include::snippets/technology-preview.adoc[] |
| 11 | + |
| 12 | +[role="_abstract"] |
| 13 | +After you configure and deploy your hosting service cluster, you can create a subscription to the SR-IOV Operator on a hosted cluster. The SR-IOV pod runs on worker machines rather than the control plane. |
| 14 | + |
| 15 | +.Prerequisites |
| 16 | + |
| 17 | +You have link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6/html/multicluster_engine/multicluster_engine_overview#hosted-control-planes-configure[configured and deployed] the hosted cluster. |
| 18 | + |
| 19 | +.Procedure |
| 20 | + |
| 21 | +. Create a namespace and an Operator group: |
| 22 | ++ |
| 23 | +[source,yaml] |
| 24 | +---- |
| 25 | +apiVersion: v1 |
| 26 | +kind: Namespace |
| 27 | +metadata: |
| 28 | + name: openshift-sriov-network-operator |
| 29 | +--- |
| 30 | +apiVersion: operators.coreos.com/v1 |
| 31 | +kind: OperatorGroup |
| 32 | +metadata: |
| 33 | + name: sriov-network-operators |
| 34 | + namespace: openshift-sriov-network-operator |
| 35 | +spec: |
| 36 | + targetNamespaces: |
| 37 | + - openshift-sriov-network-operator |
| 38 | +---- |
| 39 | + |
| 40 | +. Create a subscription to the SR-IOV Operator: |
| 41 | ++ |
| 42 | +[source,yaml] |
| 43 | +---- |
| 44 | +apiVersion: operators.coreos.com/v1alpha1 |
| 45 | +kind: Subscription |
| 46 | +metadata: |
| 47 | + name: sriov-network-operator-subsription |
| 48 | + namespace: openshift-sriov-network-operator |
| 49 | +spec: |
| 50 | + channel: "4.12" |
| 51 | + name: sriov-network-operator |
| 52 | + config: |
| 53 | + nodeSelector: |
| 54 | + node-role.kubernetes.io/worker: "" |
| 55 | + source: s/qe-app-registry/redhat-operators |
| 56 | + sourceNamespace: openshift-marketplace |
| 57 | +---- |
| 58 | + |
| 59 | +.Verification |
| 60 | + |
| 61 | +. To verify that the SR-IOV Operator is ready, run the following command and view the resulting output: |
| 62 | ++ |
| 63 | +[source,terminal] |
| 64 | +---- |
| 65 | +$ oc get csv -n openshift-sriov-network-operator |
| 66 | +---- |
| 67 | ++ |
| 68 | +.Example output |
| 69 | +[source,terminal] |
| 70 | +---- |
| 71 | +NAME DISPLAY VERSION REPLACES PHASE |
| 72 | +sriov-network-operator.4.12.0-202211021237 SR-IOV Network Operator 4.12.0-202211021237 sriov-network-operator.4.12.0-202210290517 Succeeded |
| 73 | +---- |
| 74 | + |
| 75 | +. To verify that the SR-IOV pods are deployed, run the following command: |
| 76 | ++ |
| 77 | +[source,terminal] |
| 78 | +---- |
| 79 | +$ oc get pods -n openshift-sriov-network-operator |
| 80 | +---- |
0 commit comments