additional context and links

kubernetes-sigs · Aug 20, 2024 · 477baf3 · 477baf3
1 parent e60ce08
commit 477baf3
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/docs/book/src/managed/managed.md b/docs/book/src/managed/managed.md
@@ -14,16 +14,18 @@ Documents under the Managed Clusters area:
 
 There are two APIs which can create AKS clusters and it's important to understand the differences.
 
-**ManagedCluster** - is the original API to provision AKS clusters introduced with the [0.4.4 release](https://github.com/kubernetes-sigs/cluster-api-provider-azure/releases/tag/v0.4.4).  This more closely matches the CAPI style for YAML code for other providers. The original code was based on directly using the Azure Go SDK, but in the [1.11.0 release](https://github.com/kubernetes-sigs/cluster-api-provider-azure/releases/tag/v1.11.0) was switched to utilize Azure Service Operator (ASO) as a dependency for provisioning.  This API will eventually be deprecated, [see roadmap for more information](../roadmap.md).
+**ManagedCluster** - is the original API to provision AKS clusters introduced with the [0.4.4 release](https://github.com/kubernetes-sigs/cluster-api-provider-azure/releases/tag/v0.4.4).  This more closely matches the CAPI style for YAML code for other providers. The original code was based on directly using the Azure Go SDK, but in the [1.11.0 release](https://github.com/kubernetes-sigs/cluster-api-provider-azure/releases/tag/v1.11.0) was switched to utilize Azure Service Operator (ASO) as a dependency for provisioning.  This supports the preview API, but does not natively support all AKS features available.  This API will eventually be deprecated, [see roadmap for more information](../roadmap.md).
 
-**ASOManagedCluster** - was created in the [1.15 release of CAPZ](https://github.com/kubernetes-sigs/cluster-api-provider-azure/releases/tag/v1.15.0) and creates a CAPI-compliant wrapper around the existing ASO definitions for AKS clusters.  This is the long-term plan to support provisioning AKS clusters using CAPZ.  [see roadmap for more information](../roadmap.md)
+**ASOManagedCluster** - was created in the [1.15 release of CAPZ](https://github.com/kubernetes-sigs/cluster-api-provider-azure/releases/tag/v1.15.0) and creates a CAPI-compliant wrapper around the existing ASO definitions for AKS clusters.  It has 100% API coverage for the preview and current AKS APIs via the ASO AKS CRDs.  This is the long-term plan to support provisioning AKS clusters using CAPZ.  [see roadmap for more information](../roadmap.md)
 
 ### Why is ASOManagedCluster the future?
 
 The biggest challenge with ManagedCluster is attempting to keep up with the velocity of feature changes to the frequently changing AKS API.  This model requires every single feature to be added into code directly.  Even with the simplification of code to utilize ASO as a dependency, there still is quite a bit of time required to keep up with these features.  Ulitimately, this is an unsustainable path long-term.  The [asoManaged*Patches feature](managedcluster.md#warning-warning-this-is-meant-to-be-used-sparingly-to-enable-features-for-development-and-testing-that-are-not-otherwise-represented-in-the-capz-api-misconfiguration-that-conflicts-with-capzs-normal-mode-of-operation-is-possible) enables patching/adding various AKS fields via ASO to help try to fill some of these gaps, but this comes at the cost of unknown full testing.
 
 ASOManagedCluster enables 100% API coverage natively and is easy to keep up with since it is primarily a dependency update to CAPZ.  Furthermore it has the advantage of making it easier to import existing deployed clusters which have no existing CAPZ or ASO YAML code defined.
 
+For the complete history of this transition, see the [Managing Azure Resources with Azure Service Operator](https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/docs/proposals/20230123-azure-service-operator.md) and [Automate AKS Features available in CAPZ](https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/docs/proposals/20231122-automate-aks-features.md) design proposal documents.
+
 ## ASO's AKS versus CAPZ's ASOManaged AKS
 
 It is possible to not utilize CAPZ at all and simply utilize ASO to provision an [AKS cluster definition directly](https://azure.github.io/azure-service-operator/reference/containerservice/v1api20231001/#containerservice.azure.com/v1api20231001.ManagedCluster).  The advantages that CAPZ brings over this approach are the following: