Edit

Create and manage an AKS cluster with disconnected operations (preview)

This article shows you how to install the required Azure CLI extensions, create logical networks, and create, access, and delete an Azure Kubernetes Service (AKS) cluster enabled by Azure Arc for Azure Local with disconnected operations (preview).

Important

This feature is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews.

Before you continue, review the prerequisites and limitations for AKS with disconnected operations.

Create an AKS cluster

To create an AKS cluster that supports disconnected operations, see Create an AKS cluster through CLI and Create a Kubernetes cluster using the Azure portal.

Install the Azure CLI extension

Before you install the Azure CLI extension, make sure you have the following installed:

  • Azure CLI
  • Extension version:
    • customlocation: 0.1.4
    • aksarc: 1.2.23
    • stack-hci-vm: 1.11.1

Install the CLI extension by using the following commands:

az extension add --name aksarc --version 1.2.23 
az extension add --name stack-hci-vm --version 1.11.1 
az config set core.instance_discovery=false --only-show-errors

For more information, see Install the Azure CLI extension.

Sign in with Azure CLI

Use the az login command to sign in to your Azure account. For more information, see Sign in with credentials on the command line.

Create logical networks

Use the az stack-hci-vm network lnet create command to create a logical network on the virtual machine (VM) switch in Static IP configuration. For information on limitations, see Limitations.

az stack-hci-vm network lnet create \
  --subscription $subscription \
  --resource-group $resource_group \
  --custom-location $customLocationID \
  --name $lnetName \
  --vm-switch-name $vmSwitchName \
  --ip-allocation-method "Static" \
  --address-prefixes $addressPrefixes \
  --gateway $gateway \
  --dns-servers $dnsServers \
  --ip-pool-start $ipPoolStart \
  --ip-pool-end $ipPoolEnd

For more information, see Create logical networks.

Note

You can create logical networks only through CLI. The portal isn't supported. For more information, see Azure Local VM limitations.

Create the cluster

Use CLI to create the AKS cluster. For more information, see Create an AKS cluster through CLI.

To use the Azure portal, see Create a Kubernetes cluster using the Azure portal. To create the SSH keys, see Generate and store SSH keys with the Azure CLI.

Use the az aksarc create command to create a Kubernetes cluster.

az aksarc create \
  --name $aksclustername \
  --resource-group $resource_group \
  --custom-location $customlocationID \
  --vnet-ids $logicnetId \
  --generate-ssh-keys

Note

You receive JSON-formatted information about the cluster when the creation finishes.

Here's a sample script to create logical networks and an AKS cluster.

# Check and update variables according to your environment.

$subscriptionId = " "  # Update the Starter Subscription Id of your environment
$location = "autonomous"
$resourceGroupName = " " # Update the resource group name
$customLocationResourceName = " "   # This name would be referenced in resource group
$customLocationResourceId = "/subscriptions/$SubscriptionId/resourceGroups/$resourceGroupName/providers/Microsoft.ExtendedLocation/customLocations/$customLocationResourceName"
  
# IP config detail.
 
$aszhost = <Host Machine> # update with host machine name
# YAML file would be information on the following:  
$vmSwitchName= # The value of vswitchname
$addressPrefixes= # The value of ipaddressprefix
$gateway= # The value of gateway
$dnsservers= # The value of dnsservers
$ipPoolStart= # Set this according to $addressPrefixes, don't overlap k8snodeippoolstart and k8snodeippoolend
$ipPoolEnd= # Set this according to $addressPrefixes, don't overlap k8snodeippoolstart and k8snodeippoolend
  
# Create Logical Network for AKS cluster.

$lNetName = "aksarc-lnet-static"
az stack-hci-vm network lnet create `
--resource-group $resourceGroupName `
--custom-location $customLocationResourceId `
--location $location `
--name $lNetName `
--ip-allocation-method "Static" `
--address-prefixes $addressPrefixes `
--ip-pool-start $ipPoolStart `
--ip-pool-end $ipPoolEnd `
--gateway $gateway `
--dns-servers $dnsservers `
--vm-switch-name $vmSwitchName
  
# Create AKS cluster using az cli.
 
$logicNetId = (az stack-hci-vm network lnet show --resource-group $resourceGroupName --name $lNetName --query id -o tsv)
$aksClusterName = " " # please enter the clustername
$controlPlaneIp = # Set this according to $addressPrefixes, please don't overlap $ipPoolStart and $ipPoolEnd
az aksarc create -n $aksClusterName `
--resource-group $resourceGroupName `
--custom-location $customLocationResourceId `
--node-count 2 `
--vnet-ids $logicNetId `
--generate-ssh-keys `
--control-plane-ip $controlPlaneIp `
--only-show-errors
# --node-vm-size 'Standard_D8s_v3' `

Retrieve kubeconfig

To retrieve the kubeconfig file for the AKS cluster, use the az aksarc get-credentials command. Use your admin credentials.

Here's an example:

az aksarc get-credentials --resource-group myResourceGroup --name myAKSCluster --admin

To retrieve the certificate-based admin kubeconfig for an AKS cluster Hybrid and Edge.

Here's an example:

az aksarc get-credentials \
  --name "sample-aksarccluster" \
  --resource-group "sample-rg" \
  --file C:\AksArc\config-admin \
  --adminkubectl \
  --kubeconfig C:\AksArc\config-admin get ns

For more information, see Retrieve kubeconfig.

Delete an AKS cluster

Use the az aksarc delete command to delete the AKS cluster you created.

az aksarc delete --name $aksclustername --resource-group $resource_group

Related content

  • Last updated on