virt, DPDK checkup: Label the CM and Job

In order for a user or a future UI implementation be
able to get ConfigMap and Job objects that were manually
created by oc, label them as belonging to the checkup.

Signed-off-by: Orel Misan <[email protected]>

Author: orelmisan

modules/virt-checking-cluster-dpdk-readiness.adoc

@@ -103,6 +103,8 @@ apiVersion: v1
 kind: ConfigMap
 metadata:
   name: dpdk-checkup-config
+  labels:
+    kiagnose/checkup-type: kubevirt-dpdk
 data:
   spec.timeout: 10m
   spec.param.networkAttachmentDefinitionName: <network_name> <1>
@@ -129,6 +131,8 @@ apiVersion: batch/v1
 kind: Job
 metadata:
   name: dpdk-checkup
+  labels:
+    kiagnose/checkup-type: kubevirt-dpdk
 spec:
   backoffLimit: 0
   template:
@@ -185,6 +189,8 @@ apiVersion: v1
 kind: ConfigMap
 metadata:
   name: dpdk-checkup-config
+  labels:
+    kiagnose/checkup-type: kubevirt-dpdk
 data:
   spec.timeout: 10m
   spec.param.NetworkAttachmentDefinitionName: "dpdk-network-1"