update azure static sku list

[rrangith]

What type of PR is this?

/kind bug

What this PR does / why we need it:

This regenerates the azure static sku list after #7126 removed some instance types. Particularly the standardLSv2Family which is still in use. Our cluster autoscaler is currently failing to scaleup in clusters where we use Standard_L8s_V2 for example

I just ran gen.go from westus2 and copied over the results

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Regenerate Azure static SKU list

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

[k8s-ci-robot]

Hi @rrangith. 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 /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.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[jackfrancis]

@comtalyst can you sanity check this? It's possible the previous PR ran against a non-public Azure cloud?

/lgtm

[comtalyst]

Running it on my side (public cloud) gives me something nearly the same. We would investigate #7126 later.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: comtalyst, rrangith

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:

• cluster-autoscaler/cloudprovider/azure/OWNERS [comtalyst]

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

[rrangith]

@jackfrancis @comtalyst I created some backport PRs for 1.28-1.31
#7619
#7620
#7621
#7622

[jackfrancis]

@rrangith I don't want to doubt your manual git rebase hygiene! :) But generally it's more deterministic to let the k8s-cherry-pick-bot do this work for us. Let's see if these commands yield successful PR creation outcomes:

/cherry-pick cluster-autoscaler-release-1.31
/cherry-pick cluster-autoscaler-release-1.30
/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28

[k8s-infra-cherrypick-robot]

@jackfrancis: new pull request created: #7623

In response to this:

@rrangith I don't want to doubt your manual git rebase hygiene! :) But generally it's more deterministic to let the k8s-cherry-pick-bot do this work for us. Let's see if these commands yield successful PR creation outcomes:

/cherry-pick cluster-autoscaler-release-1.31
/cherry-pick cluster-autoscaler-release-1.30
/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@jackfrancis: new pull request created: #7624

In response to this:

@rrangith I don't want to doubt your manual git rebase hygiene! :) But generally it's more deterministic to let the k8s-cherry-pick-bot do this work for us. Let's see if these commands yield successful PR creation outcomes:

/cherry-pick cluster-autoscaler-release-1.31
/cherry-pick cluster-autoscaler-release-1.30
/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@jackfrancis: new pull request created: #7625

In response to this:

@rrangith I don't want to doubt your manual git rebase hygiene! :) But generally it's more deterministic to let the k8s-cherry-pick-bot do this work for us. Let's see if these commands yield successful PR creation outcomes:

/cherry-pick cluster-autoscaler-release-1.31
/cherry-pick cluster-autoscaler-release-1.30
/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@jackfrancis: new pull request created: #7626

In response to this:

@rrangith I don't want to doubt your manual git rebase hygiene! :) But generally it's more deterministic to let the k8s-cherry-pick-bot do this work for us. Let's see if these commands yield successful PR creation outcomes:

/cherry-pick cluster-autoscaler-release-1.31
/cherry-pick cluster-autoscaler-release-1.30
/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28

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-sigs/prow repository.