In realtime checkup, if the user doesn't specify vmUnderTestContainerDiskImage, a default image is used. This should be avoided due to the risk of pulling an image version which doesn't fit the cluster/CNV versions.

OCP 4.16.0-ec.4
CNV 4.16.0 (brew.registry.redhat.io/rh-osbs/iib:697727)
kubevirt-realtime-checkup-rhel9:v4.16.0-103   

100%

1.
The cluster should be configured for RT checkup, including MCP, PerformanceProfile and permissions.
If needed - follow the U/S instructions (D/S is not available yet) in https://github.com/kiagnose/kubevirt-realtime-checkup?tab=readme-ov-file#configuration

2.
Apply a RT checkup ConfigMap without specifying the traffic-gen VM and the VM under-test images:  apiVersion: v1
kind: ConfigMap
metadata:
  name: realtime-checkup-config
data:
  spec.timeout: 10m
  spec.param.oslatDuration: 1m

3. Start the job by applying the Job resource:  apiVersion: batch/v1

kind: Job
metadata:
  name: realtime-checkup
spec:
  backoffLimit: 0
  template:
    spec:
      serviceAccountName: realtime-checkup-sa
      restartPolicy: Never
      containers:
        - name: realtime-checkup
          image: quay.io/kiagnose/kubevirt-realtime-checkup:main
          imagePullPolicy: Always
          securityContext:
            allowPrivilegeEscalation: false
            capabilities:
              drop: [ "ALL" ]
            runAsNonRoot: true
            seccompProfile:
              type: "RuntimeDefault"
          env:
            - name: CONFIGMAP_NAMESPACE
              value: yoss-ns
            - name: CONFIGMAP_NAME
              value: realtime-checkup-config
            - name: POD_UID
              valueFrom:
                fieldRef:
                  fieldPath: metadata.uid
  

The job starts (and can end successfully)

The job should immediately fail due to the absence of the spec.param.vmUnderTestContainerDiskImage parameter in the ConfigMap.