Your Browser is Out of Date

ShareDemos uses technology that works best in other browsers.
For a full experience use one of the browsers below
SR-IOV Enablement for Container Pods in OpenShift 4.3 Ready Stack

view all chapters

SR-IOV enablement
SR-IOV introduction Enable SR-IOV bits from BIOS Installing SR-IOV network operator Installing Node Feature Discovery Configuring SR-IOV network device Configuring SR-IOV network attachment Adding a Pod to the SR-IOV network

Adding a Pod to the SR-IOV network

    1. Create the Pod for the additional network created in the previous section.

    [core@csah ~]$ cat pod-vf0.yaml

    apiVersion: v1

    kind: Pod

    metadata:

      name: pod-vf0

      namespace: openshift-sriov-network-operator

      annotations:

        k8s.v1.cni.cncf.io/networks: vf0-sriov-network

    spec:

      containers:

      - name: pod-vf0

        command: ["/bin/bash", "-c", "sleep 2000000000000"]

        image: centos/tools

    [core@csah ~]$ oc create -f pod-vf0.yaml

    Follow the same step for creating another pod using the second SriovNetwork CR created on Worker node 1.

    1. Validate the success of the pod creation.

    [core@csah ~]$ oc get pods -n openshift-sriov-network-operator -o wide

    NAME                                      READY   STATUS    RESTARTS   AGE    IP                NODE                NOMINATED NODE   READINESS GATES

    network-resources-injector-nfpl5          1/1     Running   0          5d2h   10.129.0.59       etcd-2.rr5.labs     <none>           <none>

    network-resources-injector-rr6nr          1/1     Running   0          5d2h   10.130.0.60       etcd-1.rr5.labs     <none>           <none>

    network-resources-injector-vd9bc          1/1     Running   0          5d2h   10.128.0.56       etcd-0.rr5.labs     <none>           <none>

    operator-webhook-6q6sx                    1/1     Running   0          5d2h   10.129.0.58       etcd-2.rr5.labs     <none>           <none>

    operator-webhook-jtcgn                    1/1     Running   0          5d2h   10.128.0.55       etcd-0.rr5.labs     <none>           <none>

    operator-webhook-q4x46                    1/1     Running   0          5d2h   10.130.0.61       etcd-1.rr5.labs     <none>           <none>

    pod-vf0                                   1/1     Running   0          77s    10.128.2.22       worker-1.rr5.labs   <none>           <none>

    pod-vf1                                   1/1     Running   0          6s     10.131.0.44       worker-0.rr5.labs   <none>           <none>

    sriov-cni-2ntsp                           1/1     Running   0          38m    10.131.0.41       worker-0.rr5.labs   <none>           <none>

    sriov-cni-snjsl                           1/1     Running   0          39m    10.128.2.20       worker-1.rr5.labs   <none>           <none>

    sriov-device-plugin-ksbww                 1/1     Running   0          39m    192.168.111.105   worker-1.rr5.labs   <none>           <none>

    sriov-device-plugin-lb529                 1/1     Running   0          38m    192.168.111.104   worker-0.rr5.labs   <none>           <none>

    sriov-network-config-daemon-2qfrw         1/1     Running   3          5d2h   192.168.111.104   worker-0.rr5.labs   <none>           <none>

    sriov-network-config-daemon-jkjgx         1/1     Running   3          5d2h   192.168.111.105   worker-1.rr5.labs   <none>           <none>

    sriov-network-operator-554bc55b79-986c5   1/1     Running   0          5d2h   10.128.0.54       etcd-0.rr5.labs     <none>           <none>

    Make sure both the pods are created on two different worker nodes.