You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating low-priority scale sets, you can set the eviction policy to Deallocate (default) or Delete.
The Deallocate policy moves your evicted VMs to the stopped-deallocated state allowing you to redeploy evicted instances. However, there is no guarantee that the allocation will succeed. The deallocated VMs will count against your scale set instance quota and you will be charged for your underlying disks.
A brief analysis shows that {{vendor/github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2017-12-01/compute/}} does not mention EvictionPolicy, while the REST API 2017-12-01 already does support setting this parameter, which makes me a bit confused ...
Seems like it starts appearing at v19.0.0 of the azure-sdk-for-go, while the current version is v15.0.0 (last updated in April 2018).
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Mar 6, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
With low-priority scale sets, it can be interesting to set the 'eviction policy', cf https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-use-low-priority#eviction-policy.
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: