virt, vm latency checkup: Label the CM and Job

In order for the UI to 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-measuring-latency-vm-secondary-network.adoc

@@ -105,6 +105,8 @@ apiVersion: v1
 kind: ConfigMap
 metadata:
   name: kubevirt-vm-latency-checkup-config
+  labels:
+    kiagnose/checkup-type: kubevirt-vm-latency
 data:
   spec.timeout: 5m
   spec.param.networkAttachmentDefinitionNamespace: <target_namespace>
@@ -136,6 +138,8 @@ apiVersion: batch/v1
 kind: Job
 metadata:
   name: kubevirt-vm-latency-checkup
+  labels:
+    kiagnose/checkup-type: kubevirt-vm-latency
 spec:
   backoffLimit: 0
   template:
@@ -192,6 +196,8 @@ kind: ConfigMap
 metadata:
   name: kubevirt-vm-latency-checkup-config
   namespace: <target_namespace>
+  labels:
+    kiagnose/checkup-type: kubevirt-vm-latency
 data:
   spec.timeout: 5m
   spec.param.networkAttachmentDefinitionNamespace: <target_namespace>