-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
None
Use case:
In UI, we recently added an Advanced search for VirtualMachines.
This search is capable of filtering by requested CPU and requested memory. Currently the search is not working for stopped VMs that are created from InstanceType. (it is working for any running VMs, because their respective V1VirtualMachineInstance is used and also for V1VirtualMachines created from Template which have spec.template).
CPU and Memory is both extracted from domain: spec.domain || spec.template.spec.domain and then domain.cpu for CPU and domain.memory.guest || domain.resources.requests.memory for Memory.
Issue:
The issue we have is that for VMs created from the Catalog using an InstanceType, the information about requested CPU and Memory is not present in the YAML, unless we call an /expand-spec endpoint on that single VM.
We need to filter all VMs by requested CPU and requested Memory. Sending an /expand-spec request for every VM is not scalable.
We need this information in every VM YAML that we get from useK8sWatchResource hook.
Request:
We need a way to get information about requested CPU and Memory for all kinds of VMs. It should be in every spec without the necessity to call /expand-spec on VMs created from InstanceType