Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: "Quickstart: Create an Azure Kubernetes Fleet Manager and join member clusters using Bicep" description: In this quickstart, you learn how to create an Azure Kubernetes Fleet Manager and join member clusters using Bicep. ms.date: 12/16/2025 author: muhammadali ms.author: alimuhammad ms.service: azure-kubernetes-fleet-manager ms.custom: template-quickstart, mode-other ms.devlang: azurecli ms.topic: quickstart # Customer intent: As a cloud architect, I want to create an Azure Kubernetes Fleet Manager and join member clusters using Bicep, so that I can manage and orchestrate multiple Kubernetes clusters for improved scalability and application deployment. --- # Quickstart: Create an Azure Kubernetes Fleet Manager using Bicep **Applies to:** :heavy_check_mark: Fleet Manager :heavy_check_mark: Fleet Manager with hub cluster Learn how to create an Azure Kubernetes Fleet Manager using Bicep. ## Before you begin [!INCLUDE [free trial note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)] * Read the [conceptual overview of Fleet Manager](./concepts-fleet.md), which provides an explanation of fleets and member clusters referenced in this document. * An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn). * [Install or upgrade Azure CLI](/cli/azure/install-azure-cli) to version `2.71.0` or later. - Ensure **fleet** extension is updated to version `1.5.2` or higher. ## Create a Fleet Manager You can create a Fleet Manager and later add your AKS and Arc-enabled clusters as member clusters. If the Fleet Manager has a hub cluster, more features are enabled, such as [Kubernetes object propagation](./concepts-resource-propagation.md) and [Managed Fleet Namespaces](./concepts-fleet-managed-namespace.md). For more information, see the [conceptual overview of Fleet Manager types](./concepts-choosing-fleet.md), which provides a comparison of different Fleet Manager configurations. > [!IMPORTANT] > Once a Fleet Manager is created, it's possible to upgrade a Fleet Manager resource without a hub cluster to one with a hub cluster. For Fleet Manager resources with a hub cluster, once private or public is selected it can't be changed. ### [Fleet Manager without hub cluster](#tab/without-hub-cluster) If you only want to use Fleet Manager for update orchestration, you can create a hubless Fleet Manager with the following Bicep: ##### Review Bicep :::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.kubernetes/fleet-hubless/main.bicep"::: ##### Deploy the Bicep file using either Azure CLI or Azure PowerShell. 1. Save the Bicep file as **main.bicep** to your local computer. 2. Deploy the Bicep file using either Azure CLI or Azure PowerShell. ### [Azure CLI](#tab/azure-cli) ```azurecli az group create --name myResourceGroup --location eastus az deployment group create --resource-group myResourceGroup --template-file main.bicep' ``` ### [Azure PowerShell](#tab/azure-powershell) ```azurepowershell New-AzResourceGroup -Name myResourceGroup -Location eastus New-AzResourceGroupDeployment -ResourceGroupName myResourceGroup -TemplateFile ./main.bicep" ``` ### [Fleet Manager with hub cluster](#tab/with-hub-cluster) If you want to use Fleet Manager for Kubernetes object propagation in addition to update orchestration, then you need to create the Fleet Manager resource with the hub cluster. Fleet Manager with a hub cluster supports both public and private modes for network access. For more information, see [Choose an Azure Kubernetes Fleet Manager option](./concepts-choosing-fleet.md#network-access-modes-for-hub-cluster). #### Public hub cluster To create a public Fleet Manager resource with a hub cluster, use the following Bicep ##### Review Bicep :::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.kubernetes/fleet-hubful/main.bicep"::: ##### Deploy the Bicep file using either Azure CLI or Azure PowerShell. 1. Save the Bicep file as **main.bicep** to your local computer. 2. Deploy the Bicep file using either Azure CLI or Azure PowerShell. ### [Azure CLI](#tab/azure-cli) ```azurecli az group create --name myResourceGroup --location eastus az deployment group create --resource-group myResourceGroup --template-file main.bicep' ``` ### [Azure PowerShell](#tab/azure-powershell) ```azurepowershell New-AzResourceGroup -Name myResourceGroup -Location eastus New-AzResourceGroupDeployment -ResourceGroupName myResourceGroup -TemplateFile ./main.bicep" ``` #### Private hub cluster [!INCLUDE [private-fleet-prerequisites.md](./includes/private-fleet/private-fleet-prerequisites.md)] 1. Fetch Fleet Manager's service principal object ID: ```azurecli-interactive az ad sp list \ --display-name "Azure Kubernetes Service - Fleet RP" \ --query "[].{id:id}" \ --output tsv ``` ```output xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ``` 2. Review Bicep :::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.kubernetes/fleet-hubful-private/main.bicep"::: 3. Deploy the Bicep file using either Azure CLI or Azure PowerShell. Deploy the Bicep file with service principal object ID from first step: - Save the Bicep file as **main.bicep** to your local computer. - Deploy the Bicep file using either Azure CLI or Azure PowerShell. ### [Azure CLI](#tab/azure-cli) ```azurecli az group create --name myResourceGroup --location eastus az deployment group create --resource-group myResourceGroup --template-file main.bicep --parameters fleets_sp_object_id=<fleet-sp-object-id> ``` ### [Azure PowerShell](#tab/azure-powershell) ```azurepowershell New-AzResourceGroup -Name myResourceGroup -Location eastus New-AzResourceGroupDeployment -ResourceGroupName myResourceGroup -TemplateFile ./main.bicep -fleets_sp_object_id=<fleet-sp-object-id>" ``` --- ## Next steps * [Access Fleet Manager hub cluster Kubernetes API](./access-fleet-hub-cluster-kubernetes-api.md). * [Deploy cluster-scoped resources across multiple clusters](./quickstart-resource-propagation.md). * [Deploy namespace-scoped resources across multiple clusters](./quickstart-namespace-scoped-resource-propagation.md). * [Create and configure Managed Fleet Namespaces](./howto-managed-namespaces.md). * [How-to: Upgrade multiple clusters using Azure Kubernetes Fleet Manager update runs](./update-orchestration.md).