AKS MaxUnavailable Fallback Now in Preview

This article discusses the new AKS MaxUnavailable fallback feature, now in preview, which solves a common pain point with surge upgrades in Azure Kubernetes Service. When surge upgrades fail due to quota, capacity, or subnet IP constraints, the upgrade stalls. The MaxUnavailable fallback allows AKS to try the configured maxSurge, then fall back to a single surge node, and finally to an in-place upgrade using maxUnavailable. This provides a more flexible and resilient upgrade path without requiring upfront strategy decisions. The article explains how to enable it and why it matters for production clusters.