Closed mikhail-sakhnov closed 1 month ago
@sharnoff this PR is required for #1111, but we first need to have a controller version in place that overwrites current VM instances to have defaulted at the time value (qmp based scaling), as we discussed so we could enable sysfs-based scaling only for new instances when we start rolling it out. I think that aligns well with what we discussed last week about the way to update CRDs?
Impacted Packages | Coverage Δ | :robot: |
---|---|---|
github.com/neondatabase/autoscaling/neonvm/apis/neonvm/v1 | 0.56% (-0.00%) | :thumbsdown: |
github.com/neondatabase/autoscaling/pkg/neonvm/controllers | 11.73% (+0.22%) | :thumbsup: |
close in favor of #1111, which already has the changes for the current PR
Add the new field to the VirtualMachine spec, and change the VM-controller to explicitly update a VM with the default value of the field. Add temporary e2e test to ensure that VM without spec.cpuScalingMode is updated as expected.
Part of the preparations for #1082