Goal

As new features continue to be added to VMs, the number of objects they depend on continues to grow. Currently, the Object Graph statically defines the resources to include, which makes it hard to extend and maintain resources that are not handled by the main project.

This epic aims to deliver a proof-of-concept for a generic resource-addition mechanism to the VM Object Graph. This mechanism should allow cluster administrators to manually configure additional external resources to be included in the graph (for example, IPAMClaims, custom CRDs, or other third-party dependencies).

This is a POC epic and the outcome will guide the long-term plan. Potential outcomes include:

• Integrate the mechanism into the object graph and let it remain in kubevirt/kubevirt
• Keep the Object Graph in the core project but do not support external resources
• Extract the entire Object Graph feature into a separate repository

Key considerations for the POC:

• RBAC and security
• Extensibility and maintainability of the design
• Compatibility with backup/restore and cross-cluster live migration

User Stories

• As a backup partner, I want to identify all of a VM’s related objects so I can back up and restore everything the VM needs to function.
• As a VM owner, I want to see all of the objects that comprise my VM through an authoritative and centralized API.
• As a cluster admin, I want to extend the list of objects included in the graph depending on my cluster needs.
• As a VM owner, I want to migrate my VM between clusters and know exactly which dependencies must be replicated to the target cluster.

Non-Requirements

• Implementing GA support for external dependencies
• Moving the Object Graph feature to GA
• Guaranteeing that all external resources are backed up or migrated automatically