From dd959d531072c77e7809a8e4daedabfb2b17fe85 Mon Sep 17 00:00:00 2001
From: Orel Misan <omisan@redhat.com>
Date: Wed, 27 Sep 2023 11:21:27 +0300
Subject: [PATCH] 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 <omisan@redhat.com>
---
 modules/virt-measuring-latency-vm-secondary-network.adoc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/modules/virt-measuring-latency-vm-secondary-network.adoc b/modules/virt-measuring-latency-vm-secondary-network.adoc
index 8c5500e42f..2b2a55a614 100644
--- a/modules/virt-measuring-latency-vm-secondary-network.adoc
+++ b/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>