问题描述
我们的问题:由于证书，加密，域加入，TLS和密码更改，...
Our issue:The amount of time for provisioning a new instance takes a long time because of steps like certificate, encryption, domain join, TLS and Cipher changes,...
解决方案:在我们的用例中，出于部署目的，我们最终有两个不同的VMSS，即重新成像或蓝绿色用例.请注意，在我们所在的地区(Azure Gov)，我们无权访问低优先级的VMSS或Azure VM Spot进行预配置.
Solution:In our use case, we end up to have two different VMSS for the purpose of deployment, re-imaging or blue green use case. Please note in our region (Azure Gov), we don't have access to low priority VMSS or Azure VM Spot to do pre-provisioning.
仅在云原生负载均衡器(或私有流量管理器-尚不可用)后面设置两个不同的规模以根据VMSS概率准备情况路由请求是有意义的.
It only makes sense to have two different scales set behind a cloud-native load balancer (or private Traffic Manager - which is not available yet) to route request base on the VMSS prob readiness.
询问:我们如何在负载均衡器后面有两个Azure虚拟机规模集
Ask:How can we have two Azure Virtual Machine Scale Set behind a load balancer
推荐答案
我从没有尝试过，但是我不明白为什么这不适用于Standard Load Balancer(不是基本的，基本的仅限于1个vmss，不公平)，如果不行，则应与Application Gateway一起使用.
I never tried this, but I dont see why this would not work with Standard Load Balancer (not basic, basic one is limited to 1 vmss, afair), if it doesnt - it should work with Application Gateway.
这篇关于两个Azure虚拟机规模集(VMSS)之间的负载平衡的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！