Refactor docs so quick start instructions are for creating an AKS man…

[alimaazamat]

Quickstart for users should be creating a managed cluster: an aks management cluster with workload identity.

What type of PR is this?
/kind documentation

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #4768

Special notes for your reviewer:

TODOs:

• squashed commits
• includes documentation
• adds unit tests
• cherry-pick candidate

Release note:

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @alimaazamat. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.27%. Comparing base (66244df) to head (b09fdbf).
Report is 23 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5625      +/-   ##
==========================================
- Coverage   53.28%   53.27%   -0.01%     
==========================================
  Files         272      272              
  Lines       29521    29522       +1     
==========================================
  Hits        15729    15729              
- Misses      12977    12978       +1     
  Partials      815      815              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[nawazkh]

/ok-to-test

[mboersma]

Seems like we're repeating the same instructions from line 110 here?

[mbrow137]

I think this one is highlighting a different part of the Quick Start (which I can appreciate-I am partial to overexplaining)

[alimaazamat]

Same instructions but different sections. So I did Cluster API Quick Start: <"section"> to point to what specific section of the Cluster API Quick Start documentation is relevant.
Let me know how this sounds, I was thinking of merging this information in one step but in between you need to annotate the capz-manager service account and that isn't in the Cluster API Quick Start docs since that is specific to workload identity.

[mbrow137]

Since there's an in between step I wouldn't merge them for newer users. It's easier to follow that way.

[mbrow137]

Matt hit on a lot of the suggestions I had to offer. So outside of those, the only other thing I can suggest is adding potential error handling could be helpful. Otherwise, looks good to me! :) Thank you again for this!

[mbrow137]

\lgtm