The autoscaler-agent <-> scheduler plugin protocol allows the autoscaler-agent to skip the metrics field if there aren't any, which typically occurs right after the VM is created.
With the changes from #750, we assumed that .Metrics will always be non-nil, meaning that it panics when .Metrics is actually nil.
Depending on the implementation, this could have been caught by #765.
The autoscaler-agent <-> scheduler plugin protocol allows the autoscaler-agent to skip the metrics field if there aren't any, which typically occurs right after the VM is created.
With the changes from #750, we assumed that .Metrics will always be non-nil, meaning that it panics when .Metrics is actually nil.
Depending on the implementation, this could have been caught by #765.