Set NetworkInterfaces and Subnets to nil before updating Azure security groups

[codablock]

What this PR does / why we need it: This is a workaround until we have an upstream fix in azure-sdk-for-go/go-autorest. Corresponding issues are #40332 and Azure/go-autorest#112

In k8s 1.5.2, an update to azure-sdk-for-go was cherry-picked, which broke creation/updating of LBs on Azure. As we should have it back to a working state ASAP, I'd like to do a workaround for now and later when the upstream fix comes in, remove the workaround again.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #40332

Release note:

Fix failing load balancers in Azure

CC @colemickens

[k8s-ci-robot]

Hi @codablock. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with @k8s-bot ok to test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

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. I understand the commands that are listed here.

[k8s-reviewable]

This change is 

[colemickens]

Is this the only validation blip? I'm worried about the loadbalancer updates as well.

[codablock]

I just rechecked and retested and LB's are updated as expected. Which checking, I figured out that the same workaround was needed for the deletion path as well and added it to the PR.

[colemickens]

lgtm then.

[codablock]

@brendandburns Can you check this PR and give a LGTM maybe?

[brendandburns]

@k8s-bot ok to test

/lgtm
/approve

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

The following people have approved this PR: brendandburns

Needs approval from an approver in each of these OWNERS Files:

• pkg/cloudprovider/providers/azure/OWNERS [brendandburns]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[brendandburns]

@saad-ali fyi for the cherry-pick, we'd like to get this into 1.5.3...

[k8s-cherrypick-bot]

Removing label cherrypick-candidate because no release milestone was set. This is an invalid state and thus this PR is not being considered for cherry-pick to any release branch. Please add an appropriate release milestone and then re-add the label.

[k8s-cherrypick-bot]

Removing label cherrypick-candidate because no release milestone was set. This is an invalid state and thus this PR is not being considered for cherry-pick to any release branch. Please add an appropriate release milestone and then re-add the label.

[brendandburns]

@k8s-bot cri node e2e test this

[codablock]

I'd assume CI failure is not related to this PR.
@k8s-bot node e2e test this

[codablock]

@k8s-bot kubemark e2e test this
@k8s-bot gci gce e2e test this
@k8s-bot cvm gce e2e test this
@k8s-bot gce etcd3 e2e test this
@k8s-bot cvm gke e2e test this
@k8s-bot gci gke e2e test this

[codablock]

@k8s-bot kops aws e2e test this

[k8s-github-robot]

Automatic merge from submit-queue

[k8s-cherrypick-bot]

Commit found in the "release-1.5" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked.