AKS Node Pools and VM Scale Sets
You'll learn how AKS organizes worker nodes into logical groups backed by Azure's VM Scale Set infrastructure.
What Are Node Pools?
In AKS, a node pool is a logical group of worker nodes that share identical configuration—same VM size, disk type, operating system, and Kubernetes version. Think of node pools like different departments in a company: each department has people with similar roles and resources, but they work on different types of tasks.
When you create an AKS cluster, you start with a system node pool that runs critical Kubernetes components. You can add user node pools for your application workloads, each tailored for specific needs (CPU-intensive, GPU-enabled, memory-optimized, etc.).
The VM Scale Set Connection
Behind every AKS node pool sits an Azure VM Scale Set (VMSS). This is the infrastructure layer that actually provisions and manages the virtual machines. The relationship is direct: one node pool equals one VMSS.
VM Scale Sets handle:
- Creating and deleting VMs as you scale
- Applying uniform configuration across all nodes
- Distributing nodes across availability zones
- Automated OS updates and patching
You don't manually manage the VMSS—AKS does it for you. When you scale a node pool from 3 to 5 nodes, AKS tells the underlying VMSS to provision 2 more identical VMs.
Why This Matters
This architecture gives you flexibility: you can run different workload types on different node pools while AKS ensures each pool's infrastructure remains consistent and manageable through VMSS automation.
Key Takeaway: AKS node pools are logical groupings of worker nodes with identical configurations, each backed by an Azure VM Scale Set that handles the underlying infrastructure provisioning and lifecycle management.