AKS cluster creation in Azure - Deep Dive

Overview - AKS cluster creation

What is it?

AKS cluster creation is the process of setting up a managed Kubernetes environment on Microsoft Azure. It allows you to run containerized applications by automating the deployment, scaling, and management of Kubernetes clusters. This means you get a ready-to-use system to run your apps without handling the complex setup yourself.

Why it matters

Without AKS, managing Kubernetes clusters would require deep knowledge and manual work to configure servers, networking, and security. AKS solves this by simplifying cluster creation and maintenance, letting developers focus on building apps. This saves time, reduces errors, and makes cloud applications more reliable and scalable.

Where it fits

Before learning AKS cluster creation, you should understand basic cloud concepts and containerization. After mastering AKS clusters, you can explore advanced Kubernetes features, application deployment strategies, and cloud-native operations.

Mental Model

Core Idea

AKS cluster creation is like ordering a fully prepared kitchen where all appliances and tools are ready so you can start cooking your meals without setup hassle.

Think of it like...

Imagine you want to bake a cake but don't want to buy and set up all the baking tools yourself. AKS is like renting a kitchen that already has the oven, mixer, and ingredients ready, so you just bring your recipe and start baking.

┌───────────────────────────────┐
│         AKS Cluster           │
│ ┌───────────────┐             │
│ │ Control Plane │             │
│ │ (Managed by  │             │
│ │ Azure)       │             │
│ └───────────────┘             │
│ ┌───────────────┐             │
│ │ Worker Nodes  │             │
│ │ (Run your    │             │
│ │ containers)  │             │
│ └───────────────┘             │
└───────────────────────────────┘

Build-Up - 6 Steps

1

Foundation

Understanding Kubernetes Basics

Concept: Learn what Kubernetes is and why it manages containers.

Kubernetes is a system that helps run many containers across multiple computers. It handles starting, stopping, and scaling containers automatically. Containers package your app and its environment so it runs the same everywhere.

Result

You know Kubernetes is the tool AKS uses to run containerized apps.

Understanding Kubernetes basics is essential because AKS builds on it to provide managed clusters.

2

Foundation

Azure Cloud Fundamentals

Concept: Know the basics of Azure services and resources.

Azure is Microsoft's cloud platform offering virtual machines, storage, and networking. You create resources like virtual networks and storage accounts to support your apps. AKS runs inside Azure, so you need to understand how Azure organizes resources.

Result

You can navigate Azure portal and understand resource groups and subscriptions.

Knowing Azure fundamentals helps you create and manage AKS clusters within the cloud environment.

3

Intermediate

Creating an AKS Cluster Step-by-Step

🤔Before reading on: do you think creating an AKS cluster requires manual setup of all nodes or is it automated by Azure? Commit to your answer.

Concept: Learn how to create an AKS cluster using Azure tools.

You create an AKS cluster by specifying parameters like cluster name, node count, and node size. Azure automates provisioning the control plane and worker nodes. You can use Azure CLI commands like 'az aks create' or the Azure portal to start the cluster.

Result

A running Kubernetes cluster managed by Azure, ready to deploy containers.

Knowing that Azure automates cluster setup saves you from complex manual configuration and speeds up deployment.

4

Intermediate

Configuring Networking and Security

🤔Before reading on: do you think AKS clusters are open to the internet by default or secured automatically? Commit to your answer.

Concept: Understand how AKS handles networking and security during creation.

AKS creates a virtual network for your cluster nodes and configures network policies. It also sets up role-based access control (RBAC) to limit who can manage the cluster. You can enable features like Azure Active Directory integration for secure access.

Result

A secure cluster with controlled network access and user permissions.

Recognizing built-in security features helps prevent accidental exposure and protects your applications.

5

Advanced

Scaling and Upgrading AKS Clusters

🤔Before reading on: do you think scaling an AKS cluster requires downtime or can it happen live? Commit to your answer.

Concept: Learn how to change cluster size and update Kubernetes versions safely.

You can scale your AKS cluster by adding or removing nodes using commands or portal. Azure handles this without downtime. Upgrading Kubernetes versions is also managed by Azure, ensuring compatibility and minimal disruption.

Result

A cluster that grows or updates smoothly to meet demand and stay secure.

Understanding live scaling and upgrades helps maintain availability and performance in production.

6

Expert

Customizing Node Pools and Advanced Features

🤔Before reading on: do you think all nodes in an AKS cluster must be identical or can you mix different types? Commit to your answer.

Concept: Explore how to create multiple node pools with different VM sizes and features.

AKS supports multiple node pools, letting you run different workloads on specialized nodes. For example, GPU nodes for AI tasks and standard nodes for web apps. You can also configure auto-scaling and spot instances for cost savings.

Result

A flexible cluster optimized for diverse workloads and cost efficiency.

Knowing how to customize node pools unlocks powerful resource management and cost control.

Under the Hood

AKS works by Azure managing the Kubernetes control plane components like API server, scheduler, and etcd database on your behalf. It provisions virtual machines as worker nodes inside your Azure subscription, connects them via virtual networks, and installs Kubernetes agents. Azure continuously monitors and maintains the cluster health, applying updates and scaling nodes as requested.

Why designed this way?

Managing Kubernetes control plane is complex and error-prone. Azure designed AKS to offload this responsibility from users, providing a reliable, secure, and scalable Kubernetes service. This design balances user control over workloads with managed infrastructure, reducing operational overhead.

┌───────────────────────────────┐
│        Azure Control Plane     │
│ ┌───────────────┐             │
│ │ API Server    │◄────────────┤
│ │ Scheduler     │             │
│ │ etcd Storage  │             │
│ └───────────────┘             │
│               ▲               │
│               │ Managed by    │
│               │ Azure         │
│ ┌───────────────┐             │
│ │ Worker Nodes  │             │
│ │ (VMs running  │             │
│ │ kubelet agent)│             │
│ └───────────────┘             │
└───────────────────────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Do you think AKS clusters require you to manage the Kubernetes control plane yourself? Commit to yes or no.

Common Belief: AKS users must install and maintain the Kubernetes control plane components manually.

Reality: Azure fully manages the Kubernetes control plane in AKS, so users only manage the worker nodes and workloads.

Why it matters: Believing this leads to unnecessary effort and confusion, preventing users from leveraging AKS's managed benefits.

Quick: Do you think AKS clusters are free to run without any cost? Commit to yes or no.

Common Belief: AKS clusters are free because Azure manages them.

Reality: While the control plane is free, you pay for the worker nodes (VMs) and other resources used by the cluster.

Why it matters: Misunderstanding costs can cause unexpected bills and budgeting issues.

Quick: Do you think scaling an AKS cluster always causes downtime? Commit to yes or no.

Common Belief: Adding or removing nodes in AKS requires stopping the cluster or causes downtime.

Reality: AKS supports live scaling without downtime by adding or removing nodes seamlessly.

Why it matters: Thinking scaling causes downtime may prevent users from adjusting resources to meet demand efficiently.

Quick: Do you think all nodes in an AKS cluster must be identical? Commit to yes or no.

Common Belief: All nodes in an AKS cluster have to be the same size and type.

Reality: AKS supports multiple node pools with different VM sizes and configurations within the same cluster.

Why it matters: Missing this limits cluster flexibility and resource optimization.

Expert Zone

1

AKS control plane is highly available and patched by Azure without user intervention, but worker nodes require user attention for OS and application updates.

2

Using multiple node pools allows workload isolation and cost optimization but requires careful scheduling and labeling of pods.

3

Enabling Azure Active Directory integration for AKS clusters adds enterprise-grade security but requires additional setup and permissions management.

When NOT to use

AKS is not ideal if you need full control over Kubernetes internals or want to run clusters outside Azure. In such cases, self-managed Kubernetes or other cloud providers might be better. Also, for very small or simple container workloads, Azure Container Instances might be simpler and cheaper.

Production Patterns

In production, teams use Infrastructure as Code tools like Terraform or Azure ARM templates to create and manage AKS clusters consistently. They implement CI/CD pipelines to deploy apps, use monitoring tools like Azure Monitor, and configure autoscaling and node pools for cost and performance optimization.

Connections

Infrastructure as Code

builds-on

Understanding AKS cluster creation helps grasp how Infrastructure as Code automates cloud resource provisioning, making deployments repeatable and reliable.

DevOps Continuous Deployment

builds-on

Knowing AKS clusters enables smoother integration with CI/CD pipelines, automating app delivery and updates in cloud environments.

Supply Chain Management

analogy

Just like AKS manages complex container orchestration, supply chain management coordinates many moving parts to deliver products efficiently, showing how orchestration principles apply across domains.

Common Pitfalls

#1 Creating an AKS cluster without specifying a resource group.

Wrong approach:

az aks create --name myCluster --node-count 3 --enable-addons monitoring

Correct approach:

az aks create --resource-group myResourceGroup --name myCluster --node-count 3 --enable-addons monitoring

Root cause:

Not specifying a resource group causes the command to fail because Azure needs to know where to place the cluster resources.

#2 Assuming the cluster is ready immediately after creation without waiting for provisioning.

Wrong approach:

kubectl get nodes immediately after 'az aks create' command finishes.

Correct approach:

Wait for cluster provisioning to complete, then run 'az aks get-credentials' to configure kubectl before checking nodes.

Root cause:

Misunderstanding that cluster creation is asynchronous and requires setup time before use.

#3 Exposing the Kubernetes API server publicly without network restrictions.

Wrong approach:

Creating AKS cluster with '--enable-public-fqdn' and no network policies.

Correct approach:

Use private cluster option or configure network policies and firewall rules to restrict API access.

Root cause:

Lack of awareness about security best practices leads to exposing the cluster to potential attacks.

Key Takeaways

AKS cluster creation simplifies running Kubernetes by managing the control plane and automating node provisioning.

Azure handles complex setup tasks, letting you focus on deploying and scaling containerized applications.

Security and networking are built-in but require proper configuration to protect your cluster and workloads.

Scaling and upgrading AKS clusters happen smoothly without downtime, supporting production needs.

Advanced features like multiple node pools enable flexible and cost-effective resource management.