Skip to content

Add note for fleetsMember reference in ASOManagedCluster #5341

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 20, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/book/src/managed/managedcluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -306,6 +306,14 @@ The `managerName` and `managerResourceGroup` fields are the name and resource gr

When the `fleetMember` field is included, CAPZ will create an AKS fleet member resource which will join the CAPZ cluster to the AKS fleet. The AKS fleet member resource will be created in the same resource group as the CAPZ cluster.

<aside class="note">

<h1> Note </h1>

When attempting to create a cluster using `AzureASOManagedControlPlane` and adding it to an AKS fleet, the fleet manager should be referenced by the `armId` field in the ASO owner reference. See [#5333](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/5333#issuecomment-2539303793) for more information.

</aside>

### AKS Extensions

CAPZ supports enabling AKS extensions on your managed AKS clusters. Cluster extensions provide an Azure Resource Manager driven experience for installation and lifecycle management of services like Azure Machine Learning or Kubernetes applications on an AKS cluster. For more documentation on AKS extensions, refer [AKS Docs](https://learn.microsoft.com/azure/aks/cluster-extensions).
Expand Down
Loading