Pengfei Ni
Pengfei Ni
/azp run kubernetes-sigs.cloud-provider-azure.basic_lb
Refer https://github.com/Azure/aks-engine/issues/4392#issuecomment-829781415: per my understanding, service tags is used for NSG, instead of allocating IPs from a range. We need an API from network side to allow such allocations.
This is actually the common behavior for most Azure services. To avoid unexpected deletion of Azure resources, the deletion would be blocked if they are still referenced by another resources....
If the PE is created in the MC_ resource group, then they should share the same lifecycle. But if the PE is outside, then AKS would not have the permission...
No, it is actually same for other resources under node resource group. If they are referenced by other things outside of node resource group, customers need to unlink them before...
At least the default one when `loadBalancerClass` is not specified and skip when it is set to other values. For non-default ones, we need to validate what sets of LoadBalancers...
the new property is not available in Azure Go SDK yet. /hold
this is still not supported yet.
+ @MartinForReal to have a look
> Instead, 403/404 error should be checked at every GetSomeResource() inside reconcileLoadBalancer(). If it is a 403/404 error, then continue. Yes, +1 for this.