Wantong
Looks like the change is not compatible for existing services still using `service.spec.LoadBalancerIP`.
I feel a wrapper to get service LoadBalancerIP might be a solution: `getServiceLoadBalancerIP()`: ``` if annotation is set: return annotation value return service.spec.LoadBalancerIP ``` Similar function to refer would be...
Hi @phealy, I'm not sure if continuing the NSG deployment with just an event is a good idea. cx may just look at their service, see it's working without noticing...
As per discussion, we can include the correct network prefix in the route table rule and generate an event informing this.
/test pull-cloud-provider-azure-e2e-ccm-vmssflex-capz
/test pull-cloud-provider-azure-e2e-ccm-capz
/cherrypick release-1.29
/cherrypick release-1.28
/cherrypick release-1.27
/cherrypick release-1.26