GKE Node Pools and Machine Types
What you'll learn: How to configure and manage node pools with different machine types and disk settings in Google Kubernetes Engine to optimize your cluster's performance and cost.
What Are Node Pools?
In GKE, a node pool is a group of nodes (virtual machines) within your cluster that all share the same configuration. Think of node pools like parking lots designed for different vehicle types—one for compact cars, another for trucks, and another for RVs. Each serves a specific purpose with tailored specifications.
By default, GKE creates one node pool when you launch a cluster, but you can add more to handle different workload requirements.
Machine Types and Disk Configuration
Each node pool can specify:
- Machine type: The VM size (e.g.,
e2-medium,n1-standard-4,n2-highmem-8). This determines CPU cores and memory. - Disk type: Standard persistent disk or SSD persistent disk.
- Disk size: Boot disk capacity per node (minimum 100GB, typically).
For example, you might run memory-intensive databases on n2-highmem machines in one pool, while lightweight microservices run on cost-effective e2-small machines in another pool.
Node Pool Management
You can manage node pools independently without disrupting the entire cluster:
- Add new pools for specialized workloads
- Resize pools by adjusting node count (manual or autoscaling)
- Upgrade node versions pool-by-pool
- Delete unused pools to reduce costs
Node pools also support taints and node selectors, letting you control which pods land on which pool—keeping workloads isolated and properly resourced.
Key Takeaway: GKE node pools let you create heterogeneous clusters with different machine types and configurations, enabling you to match infrastructure precisely to workload needs while managing and scaling each pool independently.