Azure Loadbalancer must delete unhealthy VM of Azure VMSS
I have create Azure VMSS behind Public Azure Std LB with HTTP based Health Probe. Azure Loadbalancer is working as per expectation. But If VM is unhealthy then it must be deleted or re-provisioned. So that machine can attain healthy state again.
I’d like to ask you for more feedback on this request please. Load Balancer doesn’t control the VMSS. I think what you’re looking for is a way for VMSS to replace any instances with a LB health probe status of 0. I’ve reached out to VMSS team to get their input. LB is likely not the right place to do this.
We are building Scalesets moving our VMs from another provider and this is an extremely critical feature we need. Any update on when this will be completed.
Any updates? this is a crucial feature
any updates on this?
An idle unhealthy VM sitting there will be wasting resources. Although autoscale rules can be configured ,it can be limited by Max vms in scale set and thus doesn't reflect the actual number of healthy vms in max VMs state.
This might evolve to a performance risk
Michael Frank commented
"Load Balancer doesn’t control the VMSS" This is incorrect. For scale set upgrades the load balancer probe does control the process of rolling or automatic upgrades. This should also be extended to replace unhealthy nodes.
"I think what you’re looking for is a way for VMSS to replace any instances with a LB health probe status of 0"
"LB is likely not the right place to do this."
This is correct. The VMSS needs to be aware of the health status of the VMs it is managing (exactly as ASGs function on AWS) this allows auto-healing of Scale Sets for any use-case whether they use LBs or not.
Same applies with service gateway and need to handled as feature.
This is a big issue left unhealthy VM on LB need to be remove and repalce.
Can you please suggest best possible solution for this or otherwise please implement it !
Biren Negi commented
suggestion is valid Microsoft should be add this fetuses
For more details please go through this link https://github.com/MicrosoftDocs/azure-docs/issues/29000
Deepak Kumar commented
Or at least must have some option to trigger custom script