Specifying memory/vmi, cpu/vmi, or instances/vmi is not translated to requests.memory/vmi, requests.cpu/vmi, and requests.instances/vmi, and values are passed down to generated RequestQuota

ResourceQuota supports cpu -> requests.cpu & memory -> requests.memory

4.18.0

100%

1. Create AAQ & AARQ
2. Create VM
3. Observe AARQ and ResourceQuota statuses

memory/vmi, cpu/vmi, instances/vmi are ignored by AAQ and applied to the generated ResourceQuota object

From documentation: The ApplicationAwareResourceQuota API is compatible with the native ResourceQuota object and shares the same specification and status definitions.

memory/vmi should map to requests.memory/vmi
cpu/vmi should map to requests.cpu/vmi

Would be nice to have option to specify instances/vmi via shorthand as well

AAQ eg: DedicatedVirtualResources

Admin created AARQ:
status:
  hard:
    memory: 900Mi
    instances/vmi: '2'
    memory/vmi: 800Mi
    cpu: '10'
    requests.memory: 900Mi
    cpu/vmi: '10'
    limit.instances/vmi: '2'
    pods: '2'
    requests.memory/vmi: 800Mi
    count/pods: '2'
    requests.instances/vmi: '2'
    limits.memory: 900Mi
    limits.memory/vmi: 800Mi
    count/virtualmachines.kubevirt.io: '2'
  used:
    memory: '0'
    cpu: '0'
    requests.memory: '0'
    pods: '0'
    requests.memory/vmi: 90Mi
    count/pods: '1'
    requests.instances/vmi: '1'
    limits.memory: '0'
    count/virtualmachines.kubevirt.io: '1'

ResourceQuota (generated by AAQ)
status:
  hard:
    count/pods: '2'
    count/virtualmachines.kubevirt.io: '2'
    cpu/vmi: '10'
    instances/vmi: '2'
    limit.instances/vmi: '2'
    memory/vmi: 800Mi
  used:
    count/pods: '1'
    count/virtualmachines.kubevirt.io: '1'