AKS LTS Moves to Kubernetes 1.37: How to Get Ahead of Azure's Forced Upgrade

Azure Kubernetes Service is positioning Kubernetes 1.37, generally available in October 2026, as its newest Long Term Support option, with community support through October 2027 and Premium-tier LTS through October 2028. Beginning June 1, 2027, AKS will automatically upgrade clusters that remain unsupported after a 60-day grace period, without an opt-out and potentially outside maintenance windows, bypassing deprecated API checks and overriding PodDisruptionBudgets during stalled node drains. The article advises teams to inventory cluster versions and support dates, scan live workloads and manifests for deprecated APIs, review add-ons, webhooks, capacity, and disruption budgets, and rehearse upgrades on production-like temporary clusters. It recommends maintaining supported versions through the stable auto-upgrade channel, tuning node-pool surge capacity, upgrading control planes before node pools, and treating a parallel cluster and traffic shift as the rollback strategy because AKS does not support downgrades. While LTS can provide security backports and scheduling flexibility for regulated, stateful, or vendor-constrained workloads, it costs roughly $0.50 more per cluster hour than Standard and may accumulate larger upgrade risk over time; the preferred approach for most teams is continuous N-1 version tracking with clear ownership, automation, and regular upgrade testing.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.