VM info should be available on runner pod, so scheduler doesn't need to watch VMs
sharnoff opened this issue · comments
Em Sharnoff commented
Problem description / Motivation
There's a lot of complication in the scheduler and our Watch
implementation that comes from needing to Relist()
to synchronize state (see #851). It'd be nice if we could just look at a single object source, rather than trying to link two of them together.
Feature idea(s) / DoD
Similar to the vm.neon.tech/usage
annotation, all of the information extracted and used in api.VmInfo
should be available from annotations & labels on the pod, without consulting the VirtualMachine object.
Implementation ideas
Probably can do something similar to vm.neon.tech/usage
.