Announcing AKS Automatic managed system node pools (preview) and the Pod readiness SLA
In Azure Kubernetes Service (AKS), nodes with the same configuration (operating system and VM size) are grouped into node pools. AKS clusters use two node pool modes: system node pools host critical platform components that keep your cluster running, while user node pools run your application workloads. Traditionally, you manage both types yourself. You select VM sizes, set node counts, configure autoscaling, and plan capacity for system components. As your cluster grows or workload requirements change, you must revisit these settings to maintain resiliency.
AKS Automatic simplifies this by enabling teams to ship applications with production-grade defaults from day one. With managed system node pools (preview), AKS takes this further. The system pool is now fully managed by Microsoft. Core cluster components run on Microsoft-owned infrastructure, so you no longer provision, patch, or scale system nodes. You focus on your apps while AKS handles the operational overhead of keeping the cluster healthy.
Automatic clusters with managed system node pools also introduce the Pod readiness Service Level Agreement (SLA). Beyond API server uptime, AKS now guarantees your pods reach readiness and serve users.