الملاحظات تحرير

Quickstart: Set up an Azure Kubernetes Service host on Azure Stack HCI and deploy a workload cluster using PowerShell

  • مقالة
  • قراءة خلال 8 دقائق

Applies to: Azure Stack HCI, versions 21H2 and 20H2; Windows Server 2022 Datacenter, Windows Server 2019 Datacenter

In this quickstart, you'll learn the setup for an Azure Kubernetes Service (AKS) host. You will create AKS on Azure Stack HCI clusters using PowerShell. To use Windows Admin Center instead, see Set up with Windows Admin Center.

Note

Before you begin

  • Make sure you have satisfied all the prerequisites on the system requirements page.
  • Use an Azure account to register your AKS host for billing. For more information, visit Azure requirements.
  • Make sure you have at least one of the following access levels to the Azure subscription you use for AKS on Azure Stack HCI:
    • A user account with the built-in Owner role. You can check your access level by navigating to your subscription, clicking on "Access control (IAM)" on the left-hand side of the Azure portal and then clicking on "View my access".
    • A service principal with either the built-in Kubernetes Cluster - Azure Arc Onboarding role (minimum), the built-in Contributer role, or the built-in Owner role.
    • Your subscription should specify an Azure resource group in the Australia East, East US, Southeast Asia, or West Europe Azure region, available before registration, on the subscription mentioned above.
  • Use at least one of the following:
    • Azure Stack HCI cluster
    • Windows Server 2019/2022 Datacenter failover cluster

    Note

    We recommend having an Azure Stack HCI cluster. If you don't have any of the above, follow instructions on the Azure Stack HCI registration page.

Install the AksHci PowerShell module

If you have not installed the AksHci PowerShell module, run the following commands to install the modules.

Important

You must close all existing PowerShell windows and open a fresh administrative session to install the pre-requisite PowerShell packages and modules.

Install-Module -Name Az.Accounts -Repository PSGallery -RequiredVersion 2.2.4
Install-Module -Name Az.Resources -Repository PSGallery -RequiredVersion 3.2.0
Install-Module -Name AzureAD -Repository PSGallery -RequiredVersion 2.0.2.128
Install-Module -Name AksHci -Repository PSGallery

Import-Module Az.Accounts
Import-Module Az.Resources
Import-Module AzureAD
Import-Module AksHci

If you are using remote PowerShell, you must use CredSSP.

Important

You must close all existing PowerShell windows again to ensure that loaded modules are refreshed. Please do not continue to the next step until you have closed all PowerShell windows.

Validate your installation.

Important

Close all PowerShell windows and reopen a new administrative session to check if you have the latest version of the PowerShell module.

Get-Command -Module AksHci

To view the complete list of AksHci PowerShell commands, see AksHci PowerShell.

On all nodes in your Azure Stack HCI cluster

Run the following command on all nodes in your Azure Stack HCI cluster.

Install-PackageProvider -Name NuGet -Force 
Install-Module -Name PowershellGet -Force -Confirm:$false -SkipPublisherCheck

Install the AKS-HCI PowerShell module by running the following command on all nodes in your Azure Stack HCI cluster.

Install-Module -Name AksHci -Repository PSGallery

Register the resource provider to your subscription

Before the registration process, you need to enable the appropriate resource provider in Azure for AKS on Azure Stack HCI registration. To do that, run the following PowerShell commands.

To log in to Azure, run the Connect-AzAccount PowerShell command:

Connect-AzAccount

If you want to switch to a different subscription, run the Set-AzContext PowerShell command:

Set-AzContext -Subscription "xxxx-xxxx-xxxx-xxxx"

Run the following command to register your Azure subscription to Azure Arc enabled Kubernetes resource providers. This registration process can take up to 10 minutes, but it only needs to be performed once on a specific subscription.

Register-AzResourceProvider -ProviderNamespace Microsoft.Kubernetes
Register-AzResourceProvider -ProviderNamespace Microsoft.KubernetesConfiguration

To validate the registration process, run the following PowerShell command:

Get-AzResourceProvider -ProviderNamespace Microsoft.Kubernetes
Get-AzResourceProvider -ProviderNamespace Microsoft.KubernetesConfiguration

Step 1: Prepare your machine(s) for deployment

Run checks on every physical node to see if all the requirements are satisfied to install AKS on Azure Stack HCI. Open PowerShell as an administrator and run the following Initialize-AksHciNode command. Run the following command on all nodes in your Azure Stack HCI cluster.

Initialize-AksHciNode

Step 2: Create a virtual network

Run the following commands in step 2 on any one node in your Azure Stack HCI cluster.

To get the names of your available switches, run the following command. Make sure the SwitchType of your VM switch is "External".

Get-VMSwitch

Sample Output:

Name        SwitchType     NetAdapterInterfaceDescription
----        ----------     ------------------------------
extSwitch   External       Mellanox ConnectX-3 Pro Ethernet Adapter

To create a virtual network for the nodes in your deployment to use, create an environment variable with the New-AksHciNetworkSetting PowerShell command. This will be used later to configure a deployment that uses static IP. If you want to configure your AKS deployment with DHCP, visit New-AksHciNetworkSetting for examples. You can also review some networking node concepts.

#static IP
$vnet = New-AksHciNetworkSetting -name myvnet -vSwitchName "extSwitch" -k8sNodeIpPoolStart "172.16.10.1" -k8sNodeIpPoolEnd "172.16.10.255" -vipPoolStart "172.16.255.0" -vipPoolEnd "172.16.255.254" -ipAddressPrefix "172.16.0.0/16" -gateway "172.16.0.1" -dnsServers "172.16.0.1" -vlanId 9

Note

The values given in this example command will need to be customized for your environment.

Step 3: Configure your deployment

Run the following commands in step 3 on any one node in your Azure Stack HCI cluster.

To create the configuration settings for the AKS host, use the Set-AksHciConfig command. You must specify the imageDir, workingDir, and cloudConfigLocation parameters. If you want to reset your configuration details, run the command again with new parameters.

Configure your deployment with the following command.

Set-AksHciConfig -imageDir c:\clusterstorage\volume1\Images -workingDir c:\ClusterStorage\Volume1\ImageStore -cloudConfigLocation c:\clusterstorage\volume1\Config -vnet $vnet -cloudservicecidr "172.16.10.10/16"

Note

The values given in this example command will need to be customized for your environment.

Step 4: Log in to Azure and configure registration settings

Run the following Set-AksHciRegistration PowerShell command with your subscription and resource group name to log into Azure. You must have an Azure subscription, and an existing Azure resource group in the Australia East, East US, Southeast Asia, or West Europe Azure regions to proceed.

Set-AksHciRegistration -subscriptionId "<subscriptionId>" -resourceGroupName "<resourceGroupName>"

Step 5: Start a new deployment

Run the following command in step 5 on any one node in your Azure Stack HCI cluster.

After you've configured your deployment, you must start it in order to install the AKS on Azure Stack HCI agents/services and the AKS host. To begin deployment, run the following command.

Tip

To see additional status detail during installation, set $VerbosePreference = "Continue" before proceeding.

Install-AksHci

Warning

During installation of your Azure Kuberenetes Service host, a Kubernetes - Azure Arc resource type is created in the resource group that's set during registration. Do not delete this resource as it represents your Azure Kuberenetes Service host. You can identify the resource by checking its distribution field for a value of aks_management. Deleting this resource will result in an out-of-policy deployment.

Step 6: Create a Kubernetes cluster

After installing your AKS host, you are ready to deploy a Kubernetes cluster. Open PowerShell as an administrator and run the following New-AksHciCluster command. This example command will create a new Kubernetes cluster with one Linux node pool named linuxnodepool with a node count of 1. To read more information about node pools, visit Use node pools in AKS on Azure Stack HCI.

New-AksHciCluster -name mycluster -nodePoolName linuxnodepool -nodeCount 1 -osType Linux

Check your deployed clusters

To get a list of your deployed Kubernetes clusters, run the following Get-AksHciCluster PowerShell command.

Get-AksHciCluster

Output

ProvisioningState     : provisioned
KubernetesVersion     : v1.20.7
NodePools             : linuxnodepool
WindowsNodeCount      : 0
LinuxNodeCount        : 0
ControlPlaneNodeCount : 1
Name                  : mycluster

To get a list of the node pools in the cluster, run the following Get-AksHciNodePool PowerShell command.

Get-AksHciNodePool -clusterName mycluster

ClusterName  : mycluster
NodePoolName : linuxnodepool
Version      : v1.20.7
OsType       : Linux
NodeCount    : 1
VmSize       : Standard_K8S3_v1
Phase        : Deployed

Step 7: Connect your cluster to Arc enabled Kubernetes

Connect your cluster to Arc enabled Kubernetes by running the Enable-AksHciArcConnection command. The below example connects your AKS on Azure Stack HCI cluster to Arc using the subscription and resource group details you passed in the Set-AksHciRegistration command.

Connect-AzAccount
Enable-AksHciArcConnection -name mycluster

Note

If you encounter issues or error messages during the installation process, see installation known issues and errors for more information.

Scale a Kubernetes cluster

If you need to scale your cluster up or down, you can change the number of control plane nodes using the Set-AksHciCluster command, and you can change the number of Linux or Windows worker nodes in your node pool using the Set-AksHciNodePool command.

To scale control plane nodes, run the following command.

Set-AksHciCluster -name mycluster -controlPlaneNodeCount 3

To scale the worker nodes in your node pool, run the following command.

Set-AksHciNodePool -clusterName mycluster -name linuxnodepool -count 3

Note

In previous versions of AKS on Azure Stack HCI, the Set-AksHciCluster command was also used to scale worker nodes. AKS on Azure Stack HCI is introducing node pools in workload clusters now, so this command can only be used to scale worker nodes if your cluster was created with the old parameter set in New-AksHciCluster. To scale worker nodes in a node pool, use the Set-AksHciNodePool command.

Access your clusters using kubectl

To access your Kubernetes clusters using kubectl, run the Get-AksHciCredential PowerShell command. This will use the specified cluster's kubeconfig file as the default kubeconfig file for kubectl. You can also use kubectl to deploy applications using Helm.

Get-AksHciCredential -name mycluster

Delete a Kubernetes cluster

If you need to delete a Kubernetes cluster, run the following command.

Remove-AksHciCluster -name mycluster

Note

Make sure that your cluster is deleted by looking at the existing VMs in the Hyper-V Manager. If they are not deleted, then you can manually delete the VMs. Then, run the command Restart-Service wssdagent. This should be done on each node in the failover cluster.

Get logs

To get logs from your all your pods, run the Get-AksHciLogs command. This command will create an output zipped folder called akshcilogs.zip in your working directory. The full path to the akshcilogs.zip folder will be the output after running the command below.

Get-AksHciLogs

In this quickstart, you learned how to set up an AKS host and create AKS on Azure Stack HCI clusters using PowerShell. You also learned how to use PowerShell to scale a Kubernetes cluster and to access clusters with kubectl.

Next steps