Make scheduling node_affinities updatable #7925
Labels
enhancement
forward/review
In review; remove label to forward
priority/2
service/compute-instances
size/s
Milestone
Community Note
Description
The Compute API allows
node_affinities
to be updated when the instance is stopped: https://cloud.google.com/compute/docs/reference/rest/v1/instances/setSchedulingThis can allow users to move VMs to sole tenancy without destroying and recreating their instances. Right now we have the field set as
ForceNew
. We should removeForceNew
from the field/sub-fields, and modify schedulingHasChange to detect changes onnode_affinities
.The API documentation states that
setScheduling
requires the instance to be stopped, but it seems that this is only true to updatenode_affinities
. We should determine if it is right to move the entiresetScheduling
call to after we stop the instance, or if the instance should only be stopped for updatingnode_affinities
.New or Affected Resource(s)
References
The text was updated successfully, but these errors were encountered: