Migrate to sdk/resourcemanager/**/arm** from services/**/mgmt/**

[CecileRobertMichon]

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Some of the azure-sdk-for-go packages used have been deprecated and replaced with newer versions of the libraries. Ref: https://github.com/Azure/azure-sdk-for-go/blob/main/documentation/MIGRATION_GUIDE.md for migration.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• cluster-api-provider-azure version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[CecileRobertMichon]

/remove-lifecycle stale

[CecileRobertMichon]

/lifecycle frozen

[CecileRobertMichon]

/assign @mboersma @nojnhuh

[mboersma]

/milestone v1.8

[CecileRobertMichon]

Summarizing status here:

We are currently exploring the route of leveraging Azure Service Operator for all Azure resources PUT/DELETEs. One advantage of this is that ASO is already using SDK v2. More on this at #3113.

@mboersma is working on a POC to migrate the async services to the SDK track 2 (this issue). @nojnhuh is working on a POC + proposal to explore introducing a dependency on ASO. The idea is to evaluate both alternatives (moving to ASO and migrating SDK track 2 with current SDK usage) as a path forward to accomplish the goal of no longer depending on SDK track 1.

The current plan is to migrate the services over one at a time (order TBD but prioritizing services where new features are blocked on this migration like managedclusters). We may also consider doing both simultaneously if we decide to go with migrating to ASO but switching over the SDK version requires less refactoring and can be done in parallel.

[dtzar]

As soon as we get more clarity on the ASO proposal, it would be good to convert this issue into more specific parts of the code where we DO need to migrate to SDK track 2.

[nojnhuh]

This issue lists the current gaps: Azure/azure-service-operator#2237

[dtzar]

Since Matt created #3409 which appears to supersede this, can we go ahead and close this issue?

[mboersma]

/close

See #3409.

[k8s-ci-robot]

@mboersma: Closing this issue.

In response to this:

/close

See #3409.

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.