An important source of data about VMs running on a secured cluster is the KubeVirt custom resources (CRs) that represent each VM. This will form the basis for ACS's inventory of VMs on each secured cluster. These CRs contain data that will likely be used to link various sources of data about a particular VM, e.g. VSOCK identifier, MAC address, or pod name.

This is how I currently envision this being implemented:

• Add a K8s informer to watch KubeVirt VirtualMachine and VirtualMachineInstance CRs
• The reconciler will extract fields from these CRs that we find interesting (initial list TBD)
• This set of fields or facts will then be sent to Central for persistence.
• The k8s informer/reconciler will likely run within Sensor
• The reconciler will create a VirtualMachine Sensor event to send to Central.