Chapter 11. DPU Operator

Procedure

1. Create the openshift-dpu-operator namespace by entering the following command:

   $ cat << EOF| oc create -f -
   apiVersion: v1
   kind: Namespace
   metadata:
     name: openshift-dpu-operator
     annotations:
       workload.openshift.io/allowed: management
   EOF

   Copy to Clipboard Toggle word wrap

2. Create an OperatorGroup custom resource (CR) by entering the following command:

   $ cat << EOF| oc create -f -
   apiVersion: operators.coreos.com/v1
   kind: OperatorGroup
   metadata:
     name: dpu-operators
     namespace: openshift-dpu-operator
   spec:
     targetNamespaces:
     - openshift-dpu-operator
   EOF

   Copy to Clipboard Toggle word wrap

3. Create a Subscription CR for the DPU Operator by entering the following command:

   $ cat << EOF| oc create -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: openshift-dpu-operator-subscription
     namespace: openshift-dpu-operator
   spec:
     channel: stable
     name: dpu-operator
     source: redhat-operators
     sourceNamespace: openshift-marketplace
   EOF

   Copy to Clipboard Toggle word wrap

Verification

1. To verify that the Operator is installed, enter the following command and then check that output shows Succeeded for the Operator:

   $ oc get csv -n openshift-dpu-operator \
     -o custom-columns=Name:.metadata.name,Phase:.status.phase

   Copy to Clipboard Toggle word wrap

2. Change to the openshift-dpu-operator project:

   $ oc project openshift-dpu-operator

   Copy to Clipboard Toggle word wrap

3. Verify the DPU Operator is running by entering the following command:

   $ oc get pods -n openshift-dpu-operator

   Copy to Clipboard Toggle word wrap

   Example output

   NAME                                               READY   STATUS    RESTARTS   AGE
   dpu-operator-controller-manager-6b7bbb5db8-7lvkj   2/2     Running   0          2m9s

   Copy to Clipboard Toggle word wrap

Procedure

1. In the OpenShift Container Platform web console, click Operators OperatorHub.
2. Select DPU Operator from the list of available Operators, and then click Install.

3. On the Install Operator page, under Installed Namespace, the Operator recommended Namespace option is preselected by default. No action is required.

   1. Click Install.

Verification

1. Navigate to the Operators Installed Operators page.

2. Ensure that DPU Operator is listed in the openshift-dpu-operator project with a Status of InstallSucceeded.

   Note

   During installation an Operator might display a Failed status. If the installation later succeeds with an InstallSucceeded message, you can ignore the Failed message.

Procedure

1. Create a DpuOperatorConfig custom resource (CR) on both the host cluster and on each of the DPU clusters. The DPU Operator in each cluster is activated after this CR is created.

2. Create a file named dpu-operator-host-config.yaml by using the following YAML:

   apiVersion: config.openshift.io/v1
   kind: DpuOperatorConfig
   metadata:
    name: dpu-operator-config 

   1

   
   spec:
    mode: host 

   2

   Copy to Clipboard Toggle word wrap

   1

   The name of the custom resource must be dpu-operator-config.

   2

   Set the value to host on the host cluster. On each DPU cluster, which runs a single MicroShift cluster per DPU, set the value to dpu.

3. Create the resource by running the following command:

   $ oc apply -f dpu-operator-host-config.yaml

   Copy to Clipboard Toggle word wrap

4. You must label all nodes that either have an attached DPU or are functioning as a DPU. On the host cluster, this means labeling all compute nodes assuming each node has an attached DPU with dpu=true. On the DPU, where each MicroShift cluster consists of a single node, label that single node in each cluster with dpu=true. You can apply this label by running the following command:

   $ oc label node <node_name> dpu=true

   Copy to Clipboard Toggle word wrap

   where:

   node_name

   Refers to the name of your node, such as worker-1.

Procedure

1. Create a sample workload on the host side by using the following YAML, save the file as workload-host.yaml:

   apiVersion: v1
   kind: Pod
   metadata:
     name: my-pod
     namespace: default
     annotations:
       k8s.v1.cni.cncf.io/networks: default-sriov-net
   spec:
     nodeSelector:
       kubernetes.io/hostname: worker-237 

   1

   
     containers:
     - name: appcntr1
       image: registry.access.redhat.com/ubi9/ubi:latest
       command: ['/bin/sh', '-c', 'sleep infinity']
       imagePullPolicy: Always
       securityContext:
         priviledged: true
         runAsNonRoot: false
         runAsUser: 0
         seccompProfile:
           type: RuntimeDefault
       resources:
         requests:
           openshift.io/dpu: '1'
         limits:
           openshift.io/dpu: '1'

   Copy to Clipboard Toggle word wrap

   1

   The name of the node where the workload is deployed.

2. Create the workload by running the following command:

   $ oc apply -f workload-host.yaml

   Copy to Clipboard Toggle word wrap

Procedure

1. Save the following YAML file example as sfc.yaml:

   apiVersion: config.openshift.io/v1
   kind: ServiceFunctionChain
   metadata:
     name: sfc
     namespace: openshift-dpu-operator
   spec:
     networkFunctions:
     - name: my-network-function 

   1

   
       image: quay.io/example-org/my-network-function:latest 

   2

   Copy to Clipboard Toggle word wrap

   1

   The name of the network function. This name is used to identify the network function in the service function chain.

   2

   The URL to the container image that contains the network function. The image must be accessible from the DPU.

2. Create the chain by running the following command on the DPU nodes:

   $ oc apply -f sfc.yaml

   Copy to Clipboard Toggle word wrap

Procedure

1. Delete the DpuOperatorConfig CR that was created by running the following command

   $ oc delete DpuOperatorConfig dpu-operator-config

   Copy to Clipboard Toggle word wrap

2. Delete the subscription that was used to install the DPU Operator by running the following command:

   $ oc delete Subscription openshift-dpu-operator-subscription -n openshift-dpu-operator

   Copy to Clipboard Toggle word wrap

3. Remove the OperatorGroup resource that was created by running the following command:

   $ oc delete OperatorGroup dpu-operators -n openshift-dpu-operator

   Copy to Clipboard Toggle word wrap

4. Uninstall the DPU Operator as follows:

   1. Check the installed Operators by running the following command:

      $ oc get csv -n openshift-dpu-operator

      Copy to Clipboard Toggle word wrap

      Example output

      NAME                                DISPLAY        VERSION               REPLACES   PHASE
      dpu-operator.v4.19.0-202503130333   DPU Operator   4.19.0-202503130333              Failed

      Copy to Clipboard Toggle word wrap

   2. Delete the DPU Operator by running the following command:

      $ oc delete csv dpu-operator.v4.19.0-202503130333 -n openshift-dpu-operator

      Copy to Clipboard Toggle word wrap

5. Delete the namespace that was created for the DPU Operator by running the following command:

   $ oc delete namespace openshift-dpu-operator

   Copy to Clipboard Toggle word wrap

Verification

1. Verify that the DPU Operator is uninstalled by running the following command. An example of succesful command output is No resources found in openshift-dpu-operator namespace.

   $ oc get csv -n openshift-dpu-operator

   Copy to Clipboard Toggle word wrap