Audit AKS Managed Cluster docs for feature-completeness

[nojnhuh]

/kind documentation
/area managedclusters

Describe the solution you'd like

I know I have not been good about adding docs for new features to managed clusters like this, so we should take a pass at the existing managed cluster docs to ensure all implemented features have adequate documentation.

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.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[nojnhuh]

/lifecycle active

[nojnhuh]

/assign

[mboersma]

/milestone v1.9

[dtzar]

IF it were reasonably possible, it would be nice to do a delta of what features/capabilities there are in the latest version of the ManagedCluster API compared to what's in CAPZ while doing this work.

[nojnhuh]

@dtzar Is that something you'd like to see persisted with the rest of the docs? Or would this be a one-time thing? I'd be hesitant to commit to keeping that kind of info up to date but I'm also not sure what a good ephemeral place for that would be.

At least for this issue, I was planning to go through what's implemented vs. documented in CAPZ without needing to enumerate all of the features currently implemented in AKS, so maybe a separate issue for that would be best.

[dtzar]

This would be a one-time thing to help us (even roughly) identify the gaps of what's missing today.
A separate issue makes sense. Maybe if you anecdotally detect those gaps, we can start to put those on a shared list somewhere?

[nojnhuh]

Sure, I'll follow up in that new issue.

[jackfrancis]

/assign