Fix standalone VM EnsureBackendPoolDeleted

[lzhecheng]

What type of PR is this?

/kind testing
/kind bug

What this PR does / why we need it:

• Fix ensureBackendPoolDeleted for standalone VM
• Trigger Service reconcile for exclude-from-external-load-balancers e2e test
• Refactor e2e
• Add logs for exclude-from-external-load-balancers

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Fix ensureBackendPoolDeleted for standalone VM

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[lzhecheng]

/retest

[nilo19]

This will add a lot of logs for large clusters. Can we change it to 6?

[lzhecheng]

I chose 4 because I think the log level should be same with the below logic:

		for _, address := range getNodePrivateIPAddresses(newNode) {
			if az.nodePrivateIPs[newNode.Name] == nil {
				az.nodePrivateIPs[newNode.Name] = sets.New[string]()
			}

			klog.V(4).Infof("adding IP address %s of the node %s", address, newNode.Name)
			az.nodePrivateIPs[newNode.Name].Insert(address)
		}

Shall we make all of them 6?

[feiskyer]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: feiskyer, lzhecheng

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [feiskyer,lzhecheng]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[lzhecheng]

/retest

[nilo19]

We can check loadBalancerBackendAddresses as well for nic lb

[lzhecheng]

I think it is a good idea but after I tried, it seems not possible.
I found that the LoadBalancerBackendAddress struct in:
https://github.com/kubernetes-sigs/cloud-provider-azure/blob/0e6c0a55c732dad2e4b8b946b234c118259769f4/vendor/github.com/Azure/azure-sdk-for-go/services/network/mgmt/2022-07-01/network/models.go
is:

type LoadBalancerBackendAddress struct {
	// LoadBalancerBackendAddressPropertiesFormat - Properties of load balancer backend address pool.
	*LoadBalancerBackendAddressPropertiesFormat `json:"properties,omitempty"`
	// Name - Name of the backend address.
	Name *string `json:"name,omitempty"`
}

It should have ID but actually not. ID is need for autoscaling cluster to avoid taking systempool into consideration.

[nilo19]

it's in properties.networkInterfaceIPConfiguration

[lzhecheng]

Thank you. Updated

[nilo19]

/lgtm

[lzhecheng]

/cherrypick release-1.27

[k8s-infra-cherrypick-robot]

@lzhecheng: #4217 failed to apply on top of branch "release-1.27":

Applying: Fix standalone VM EnsureBackendPoolDeleted * Fix ensureBackendPoolDeleted for standalone VM * Trigger Service reconcile for exclude-from-external-load-balancers e2e test * Refactor e2e * Add logs for exclude-from-external-load-balancers
Using index info to reconstruct a base tree...
M	pkg/provider/azure.go
M	pkg/provider/azure_loadbalancer.go
M	pkg/provider/azure_loadbalancer_backendpool.go
M	pkg/provider/azure_standard.go
M	tests/e2e/network/ensureloadbalancer.go
M	tests/e2e/utils/node_utils.go
Falling back to patching base and 3-way merge...
Auto-merging tests/e2e/utils/node_utils.go
CONFLICT (content): Merge conflict in tests/e2e/utils/node_utils.go
Auto-merging tests/e2e/network/ensureloadbalancer.go
CONFLICT (content): Merge conflict in tests/e2e/network/ensureloadbalancer.go
Auto-merging pkg/provider/azure_standard.go
Auto-merging pkg/provider/azure_loadbalancer_backendpool.go
Auto-merging pkg/provider/azure_loadbalancer.go
CONFLICT (content): Merge conflict in pkg/provider/azure_loadbalancer.go
Auto-merging pkg/provider/azure.go
CONFLICT (content): Merge conflict in pkg/provider/azure.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix standalone VM EnsureBackendPoolDeleted * Fix ensureBackendPoolDeleted for standalone VM * Trigger Service reconcile for exclude-from-external-load-balancers e2e test * Refactor e2e * Add logs for exclude-from-external-load-balancers
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-1.27

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.