virt, DPDK: Update runtimeClass configuration API

Following a change in HCO [0] that exposes the defaultRuntimeClass API to the user, it is now
possible to configure the defaultRuntimeClass on the cluster by editing the HCO CR.
This change avoids forcing the user to use the json-patch annotation workaround.

[0] kubevirt/hyperconverged-cluster-operator#2370

Signed-off-by: Ram Lavi <[email protected]>

Author: RamLavi

modules/virt-configuring-cluster-dpdk.adoc

@@ -89,18 +89,17 @@ The compute nodes automatically restart after you apply the `MachineConfigPool`
 $ oc get performanceprofiles.performance.openshift.io profile-1 -o=jsonpath='{.status.runtimeClass}{"\n"}'
 ----
 
-. Set the previously obtained `RuntimeClass` name as the default container runtime class for the `virt-launcher` pods by adding the following annotation to the `HyperConverged` custom resource (CR):
+. Set the previously obtained `RuntimeClass` name as the default container runtime class for the `virt-launcher` pods by editing the `HyperConverged` custom resource (CR):
 +
 [source,terminal]
 ----
-$ oc annotate --overwrite -n openshift-cnv hco kubevirt-hyperconverged \
-    kubevirt.kubevirt.io/jsonpatch='[{"op": "add", "path": "/spec/configuration/defaultRuntimeClass", "value": <runtimeclass_name>}]'
+$ oc patch -n openshift-cnv hco kubevirt-hyperconverged \
+    --type='json' -p='[{"op": "add", "path": "/spec/defaultRuntimeClass", "value":"<runtimeclass-name>"}]'
 ----
 +
 [NOTE]
 ====
-Adding the annotation to the `HyperConverged` CR changes a global setting that affects all VMs that are created after the annotation is applied.
-Setting this annotation breaches support of the {VirtProductName} instance and must be used only on test clusters. For best performance, apply for a support exception.
+Editing the `HyperConverged` CR changes a global setting that affects all VMs that are created after the change is applied.
 ====
 
 . Create an `SriovNetworkNodePolicy` object with the `spec.deviceType` field set to `vfio-pci`: