Goal

As new features continue to be added to kubevirt virtual machines, the graph of objects (DVs, PVCs, InstanceTypes, Preferences, Secrets, ConfigMaps, etc) continues to expand. Trying to identift all of the objects that a VM depends on (ie for Backup and DR) can be daunting and error prone. We should make this process easier for our users and partners.

User Stories

• As a backup partner I want a way to identify all of a VMs related objects so that I can backup and restore everything that a VM needs to function properly.
• As a VM owner I want to see all of the objects that comprise a VM "application" so that I can more easily define an ACM discovered application and protect my VM with disaster recovery software.
• As a VM owner I want to migrate my VM from one cluster to another and know authoritatively all of the dependencies that must be replicated to the target cluster.
• As a kubevirt developer I want to easily keep the object graph code updated when I introduce code that changes the relationship of a VM to its dependent objects.

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• Any additional details or decisions made/needed
• This idea is similar to 'relatedObjects' in existing resources (OLM I think has something like this, or maybe must gather, I forget)