Azure Kubernetes Service (AKS) Prerequisites

Before you can deploy and manage an Azure Kubernetes Service (AKS) cluster, there are several prerequisites and considerations that need to be met. This document outlines the essential requirements.

1. Azure Subscription

You must have an active Azure subscription. If you don't have one, you can create a free account. An Azure subscription provides access to Azure services and billing.

2. Azure CLI or Azure PowerShell

The Azure Command-Line Interface (CLI) or Azure PowerShell modules are essential tools for interacting with Azure resources, including AKS. Ensure you have one of them installed and configured.

After installation, log in to your Azure account using:

az login

Connect-AzAccount

3. Resource Group

An Azure resource group is a logical container that holds related Azure resources for a solution. You'll need a resource group to deploy your AKS cluster and its associated resources. You can create one using the Azure CLI:

az group create --name myResourceGroup --location eastus

4. Supported Kubernetes Version

AKS supports a range of Kubernetes versions. It's recommended to use a supported stable version. You can view the list of supported versions and the release cadence on the AKS documentation.

To view available Kubernetes versions for AKS in your region:

az aks get-versions --location eastus --output table

5. Network Requirements

Your AKS cluster needs to be deployed within an Azure Virtual Network (VNet). You can either create a new VNet or use an existing one. Consider the following network aspects:

IP Address Space: Ensure sufficient IP address space for your VNet and subnets to accommodate the cluster nodes, pods, and services.
Network Security Groups (NSGs): NSGs are used to filter network traffic to and from Azure resources in an Azure virtual network. AKS manages some NSGs, but you might need to configure custom rules.
Azure CNI vs. Kubenet: AKS offers two network plugins: Azure CNI and Kubenet. Azure CNI provides more advanced networking features and IP address management for pods, while Kubenet is simpler for basic deployments.

6. Permissions

The identity used to create the AKS cluster must have the necessary permissions to create and manage resources within the Azure subscription and resource group. Typically, roles like "Owner" or "Contributor" are sufficient, but custom roles can also be configured.

7. Optional: Container Registry

If you plan to deploy custom container images, you'll likely need a container registry, such as Azure Container Registry (ACR). This allows you to store, manage, and secure your container images.

Learn more about storage options

Important: Always refer to the latest official Azure documentation for the most up-to-date prerequisites and best practices, as requirements can evolve.

Next Steps

Once you have met these prerequisites, you are ready to proceed with deploying your AKS cluster.

Deploying Your First AKS Cluster