Quickstart: Create an Azure Kubernetes Fleet Manager resource and join member clusters using Azure CLI

Get started with Azure Kubernetes Fleet Manager (Fleet) by using the Azure CLI to create a Fleet resource and later connect Azure Kubernetes Service (AKS) clusters as member clusters.

If you don't have an Azure trail subscription, create a trial subscription before you begin.

• Read the conceptual overview of this feature, which provides an explanation of fleets and member clusters referenced in this document.

• Read the conceptual overview of fleet types, which provides a comparison of different fleet configuration options.

• An Azure account with an active subscription. Create an account.

• An identity (user or service principal) which can be used to log in to Azure CLI. This identity needs to have the following permissions on the Fleet and AKS resource types for completing the steps listed in this quickstart:

  • Microsoft.ContainerService/fleets/read
  • Microsoft.ContainerService/fleets/write
  • Microsoft.ContainerService/fleets/members/read
  • Microsoft.ContainerService/fleets/members/write
  • Microsoft.ContainerService/fleetMemberships/read
  • Microsoft.ContainerService/fleetMemberships/write
  • Microsoft.ContainerService/managedClusters/read
  • Microsoft.ContainerService/managedClusters/write

• Install or upgrade Azure CLI to version 2.53.1 or later.

• Install the fleet Azure CLI extension using the az extension add command and Make sure your version is at least 1.0.0.

  az extension add --name fleet
  

• Set the following environment variables:

  export SUBSCRIPTION_ID=<subscription_id>
  export GROUP=<your_resource_group_name>
  export FLEET=<your_fleet_name>
  

• Install kubectl and kubelogin using the az aks install-cli command.

  az aks install-cli
  

• The AKS clusters that you want to join as member clusters to the Fleet resource need to be within the supported versions of AKS. Learn more about AKS version support policy here.

An Azure resource group is a logical group in which Azure resources are deployed and managed. When you create a resource group, you're prompted to specify a location. This location is the storage location of your resource group metadata and where your resources run in Azure if you don't specify another location during resource creation.

Set the Azure subscription and create a resource group using the az group create command.

az account set -s ${SUBSCRIPTION_ID}
az group create --name ${GROUP} --location chinanorth3

The following output example resembles successful creation of the resource group:

{
  "id": "/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/fleet-demo",
  "location": "chinanorth3",
  "managedBy": null,
  "name": "fleet-demo",
  "properties": {
    "provisioningState": "Succeeded"
  },
  "tags": null,
  "type": "Microsoft.Resources/resourceGroups"
}

You can create a Fleet resource to later group your AKS clusters as member clusters. When created via Azure CLI, by default, this resource enables member cluster grouping and update orchestration. If the Fleet hub is enabled, other preview features are enabled, such as Kubernetes object propagation to member clusters and L4 service load balancing across multiple member clusters. For more information, see the conceptual overview of fleet types, which provides a comparison of different fleet configurations.

az fleet create --resource-group ${GROUP} --name ${FLEET} --location chinanorth3

{
  "etag": "...",
  "hubProfile": null,
  "id": "/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/fleet-demo/providers/Microsoft.ContainerService/fleets/fleet-demo",
  "identity": {
    "principalId": null,
    "tenantId": null,
    "type": "None",
    "userAssignedIdentities": null
  },
  "location": "chinanorth3",
  "name": "fleet-demo",
  "provisioningState": "Succeeded",
  "resourceGroup": "fleet-demo",
  "systemData": {
    "createdAt": "2023-11-03T17:15:19.610149+00:00",
    "createdBy": "<user>",
    "createdByType": "User",
    "lastModifiedAt": "2023-11-03T17:15:19.610149+00:00",
    "lastModifiedBy": "<user>",
    "lastModifiedByType": "User"
  },
  "tags": null,
  "type": "Microsoft.ContainerService/fleets"
}

az fleet create --resource-group ${GROUP} --name ${FLEET} --location chinanorth3 --enable-hub

{
  "etag": "...",
  "hubProfile": null,
  "id": "/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/fleet-demo/providers/Microsoft.ContainerService/fleets/fleet-demo",
  "identity": {
    "principalId": null,
    "tenantId": null,
    "type": "None",
    "userAssignedIdentities": null
  },
  "location": "eastus",
  "name": "fleet-demo",
  "provisioningState": "Succeeded",
  "resourceGroup": "fleet-demo",
  "systemData": {
    "createdAt": "2023-11-03T17:15:19.610149+00:00",
    "createdBy": "<user>",
    "createdByType": "User",
    "lastModifiedAt": "2023-11-03T17:15:19.610149+00:00",
    "lastModifiedBy": "<user>",
    "lastModifiedByType": "User"
  },
  "tags": null,
  "type": "Microsoft.ContainerService/fleets"
}

az network vnet create --resource-group ${GROUP} --name vnet --address-prefixes 192.168.0.0/16
az network vnet subnet create --resource-group ${GROUP} --vnet-name vnet --name subnet --address-prefixes 192.168.0.0/24

SUBNET_ID=$(az network vnet subnet show --resource-group ${GROUP} --vnet-name vnet -n subnet -o tsv --query id)

az fleet create --resource-group ${GROUP} --name ${FLEET} --enable-hub --enable-private-cluster --agent-subnet-id "${SUBNET_ID}"

Fleet currently supports joining existing AKS clusters as member clusters.

1. Set the following environment variables for member clusters:

   export MEMBER_NAME_1=aks-member-1
   export MEMBER_CLUSTER_ID_1=/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${GROUP}/providers/Microsoft.ContainerService/managedClusters/${MEMBER_NAME_1}
   

2. Join your existing AKS clusters to the Fleet resource using the az fleet member create command.

   # Join the first member cluster
   az fleet member create --resource-group ${GROUP} --fleet-name ${FLEET} --name ${MEMBER_NAME_1} --member-cluster-id ${MEMBER_CLUSTER_ID_1}
   

   Your output should look similar to the following example output:

   {
     "clusterResourceId": "/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<GROUP>/providers/Microsoft.ContainerService/managedClusters/aks-member-x",
     "etag": "...",
     "id": "/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<GROUP>/providers/Microsoft.ContainerService/fleets/<FLEET>/members/aks-member-x",
     "name": "aks-member-1",
     "provisioningState": "Succeeded",
     "resourceGroup": "<GROUP>",
     "systemData": {
       "createdAt": "2022-10-04T19:04:56.455813+00:00",
       "createdBy": "<user>",
       "createdByType": "User",
       "lastModifiedAt": "2022-10-04T19:04:56.455813+00:00",
       "lastModifiedBy": "<user>",
       "lastModifiedByType": "User"
     },
     "type": "Microsoft.ContainerService/fleets/members"
   }
   

3. Verify that the member clusters successfully joined the Fleet resource using the az fleet member list command.

   az fleet member list --resource-group ${GROUP} --fleet-name ${FLEET} -o table
   

   If successful, your output should look similar to the following example output:

   ClusterResourceId                                                                                                                                Name          ProvisioningState    ResourceGroup
   -----------------------------------------------------------------------------------------------------------------------------------------------  ------------  -------------------  ---------------
   /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<GROUP>/providers/Microsoft.ContainerService/managedClusters/aks-member-1  aks-member-1  Succeeded            <GROUP>
   /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<GROUP>/providers/Microsoft.ContainerService/managedClusters/aks-member-2  aks-member-2  Succeeded            <GROUP>
   /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<GROUP>/providers/Microsoft.ContainerService/managedClusters/aks-member-3  aks-member-3  Succeeded            <GROUP>
   

• Access Fleet hub cluster Kubernetes API.