AKS cluster creation in Azure - Step-by-Step Execution

Process Flow - AKS cluster creation

Start: Define cluster config

↓

Authenticate with Azure

↓

Create Resource Group

↓

Create AKS Cluster

↓

Wait for provisioning

↓

Cluster Ready

↓

Connect to cluster with kubectl

This flow shows the main steps to create an AKS cluster: define settings, authenticate, create resource group, create cluster, wait, then connect.

Execution Sample

Azure

az group create --name myResourceGroup --location eastus
az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 2 --enable-managed-identity
az aks get-credentials --resource-group myResourceGroup --name myAKSCluster

This code creates a resource group, then an AKS cluster with 2 nodes, then configures kubectl to connect to it.

Process Table

Step	Command	Action	Result	Status
1	az group create --name myResourceGroup --location eastus	Create resource group	Resource group 'myResourceGroup' created	Success
2	az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 2 --enable-managed-identity	Start AKS cluster creation	Provisioning started	In Progress
3	Waiting for provisioning	Cluster nodes and control plane are created	Cluster provisioning ongoing	In Progress
4	Provisioning completes	Cluster ready to use	AKS cluster 'myAKSCluster' created	Success
5	az aks get-credentials --resource-group myResourceGroup --name myAKSCluster	Download cluster config	kubectl configured to connect to cluster	Success

💡 Cluster is ready and kubectl is configured for access

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	Final
resourceGroup	undefined	myResourceGroup	myResourceGroup	myResourceGroup	myResourceGroup
aksCluster	undefined	undefined	provisioning	ready	ready
kubectlConfig	undefined	undefined	undefined	undefined	configured

Key Moments - 3 Insights

Why do we create a resource group before the AKS cluster?

The resource group is a container for Azure resources. The AKS cluster must be created inside a resource group. See execution_table step 1 and 2.

What does 'provisioning' mean during cluster creation?

Provisioning means Azure is setting up the cluster's control plane and nodes. This is shown in execution_table steps 2 and 3.

Why do we run 'az aks get-credentials' after cluster creation?

This command downloads cluster access info so kubectl can connect. It happens after the cluster is ready, see execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the status after starting the AKS cluster creation?

A Success

B In Progress

C Failed

D Pending

💡 Hint

Check the 'Status' column at step 2 in the execution_table.

At which step does the AKS cluster become ready to use?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look for 'Cluster ready to use' in the 'Result' column of the execution_table.

If we skip creating the resource group, what would happen?

A AKS cluster creation would fail

B Cluster would be created in default group

C kubectl would auto-configure

D Nothing, it works fine

💡 Hint

Resource group is required as shown in execution_table step 1 and 2.

Concept Snapshot

AKS cluster creation steps:
1. Create a resource group (container for resources).
2. Create AKS cluster inside that group with node count.
3. Wait for provisioning to complete.
4. Download cluster credentials to connect with kubectl.
Use 'az' CLI commands in this order for success.

Full Transcript

To create an AKS cluster, first define your cluster settings. Then authenticate with Azure. Next, create a resource group to hold your cluster. After that, run the command to create the AKS cluster with your desired node count. Wait while Azure provisions the cluster resources. Once ready, download the cluster credentials to configure kubectl. This lets you manage your cluster. Each step must succeed before moving to the next. The resource group is essential as it organizes your Azure resources. Provisioning means Azure is setting up the cluster behind the scenes. Finally, getting credentials connects your local tools to the cluster.

Practice

1. What is the main purpose of creating an AKS cluster in Azure?

easy

A. To host traditional web applications without containers

B. To create virtual machines for general computing

C. To store large amounts of unstructured data

D. To run and manage containerized applications using Kubernetes

Solution

1. Step 1: Understand AKS functionality

   AKS (Azure Kubernetes Service) is designed to run and manage containerized applications using Kubernetes orchestration.

2. Step 2: Differentiate from other Azure services

   Virtual machines, storage, and web hosting are handled by other Azure services, not AKS.

3. Final Answer:

   To run and manage containerized applications using Kubernetes -> Option D

4. Quick Check:

   AKS = Kubernetes container management [OK]

Hint: AKS is for Kubernetes container orchestration [OK]

Common Mistakes:

• Confusing AKS with VM creation
• Thinking AKS is for storage
• Assuming AKS hosts non-container apps

2. Which Azure CLI command correctly creates an AKS cluster named myCluster in resource group myGroup with 3 nodes?

easy

A. az create aks --rg myGroup --cluster-name myCluster --count 3

B. az aks create --resource-group myGroup --name myCluster --node-count 3

C. az aks new --group myGroup --cluster myCluster --nodes 3

D. az aks deploy --resource-group myGroup --name myCluster --nodes 3

Solution

1. Step 1: Identify correct Azure CLI syntax

   The correct command to create an AKS cluster uses az aks create with parameters --resource-group, --name, and --node-count.

2. Step 2: Compare options

   Only az aks create --resource-group myGroup --name myCluster --node-count 3 uses the correct command and parameter names as per Azure CLI documentation.

3. Final Answer:

   az aks create --resource-group myGroup --name myCluster --node-count 3 -> Option B

4. Quick Check:

   Correct CLI syntax = az aks create --resource-group myGroup --name myCluster --node-count 3 [OK]

Hint: Use 'az aks create' with --resource-group, --name, --node-count [OK]

Common Mistakes:

• Using wrong command verbs like 'new' or 'deploy'
• Incorrect parameter names like --group or --nodes
• Mixing command order or missing required flags

3. What will be the result of this command?

az aks create --resource-group myGroup --name myCluster --node-count 2 --enable-managed-identity --ssh-key-value ~/.ssh/id_rsa.pub

medium

A. Creates an AKS cluster with 2 nodes, managed identity, and SSH access enabled

B. Creates an AKS cluster with 2 nodes but disables SSH access

C. Fails because --enable-managed-identity is not a valid flag

D. Creates an AKS cluster with 2 nodes but without managed identity

Solution

1. Step 1: Analyze command flags

   The command uses --enable-managed-identity to enable managed identity and --ssh-key-value to set SSH public key for node access.

2. Step 2: Understand expected behavior

   This command creates a cluster with 2 nodes, managed identity enabled, and SSH access configured using the provided key.

3. Final Answer:

   Creates an AKS cluster with 2 nodes, managed identity, and SSH access enabled -> Option A

4. Quick Check:

   Managed identity + SSH key = Creates an AKS cluster with 2 nodes, managed identity, and SSH access enabled [OK]

Hint: Managed identity and SSH flags enable secure access [OK]

Common Mistakes:

• Assuming --enable-managed-identity is invalid
• Thinking SSH is disabled without extra flags
• Confusing managed identity with service principal

4. You run this command but get an error:

az aks create --resource-group myGroup --name myCluster --node-count two

What is the likely cause?

medium

A. The cluster name cannot be 'myCluster'

B. The resource group name is invalid

C. The node count must be a number, not a word

D. The command is missing the --enable-managed-identity flag

Solution

1. Step 1: Check parameter types

   The --node-count parameter expects a numeric value, but 'two' is a word, causing a syntax error.

2. Step 2: Validate other parameters

   Resource group and cluster name are valid strings; managed identity flag is optional.

3. Final Answer:

   The node count must be a number, not a word -> Option C

4. Quick Check:

   Numeric node count required = The node count must be a number, not a word [OK]

Hint: Node count must be numeric, not text [OK]

Common Mistakes:

• Using words instead of numbers for counts
• Assuming resource group or name causes error
• Thinking managed identity flag is mandatory

5. You want to create an AKS cluster with 4 nodes, enable managed identity, and use a custom SSH key located at /keys/mykey.pub. Which command is correct?

hard

A. az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity --ssh-key-value /keys/mykey.pub

B. az aks create --resource-group myGroup --name myCluster --nodes 4 --enable-msi --ssh-key /keys/mykey.pub

C. az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity

D. az aks create --resource-group myGroup --name myCluster --node-count 4 --ssh-key-value /keys/mykey.pub

Solution

1. Step 1: Verify required parameters

   The command must specify --node-count 4, --enable-managed-identity, and --ssh-key-value with the correct path.

2. Step 2: Check option correctness

   az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity --ssh-key-value /keys/mykey.pub uses correct parameter names and includes all required flags. Other options have incorrect flags or missing parameters.

3. Final Answer:

   az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity --ssh-key-value /keys/mykey.pub -> Option A

4. Quick Check:

   Correct flags and values = az aks create --resource-group myGroup --name myCluster --node-count 4 --enable-managed-identity --ssh-key-value /keys/mykey.pub [OK]

Hint: Use full flag names and correct SSH key path [OK]

Common Mistakes:

• Using shorthand or incorrect flags like --nodes or --ssh-key
• Omitting managed identity flag
• Forgetting to specify SSH key path