Skip to content

Version Support

AKS version support is an operational calendar you should query continuously, not a static table you read once per year.

Topic/Command Groups

flowchart TD
    A[Current cluster version] --> B{Within N N-1 or N-2?}
    B -->|Yes| C[Stay current on latest supported patch]
    B -->|No| D{Within N-3 platform support?}
    D -->|Yes| E[Accelerate upgrade or LTS plan]
    D -->|No| F[Recovery path or cluster replacement]

Support states to track

  • GA support window: N, N-1, N-2.
  • Platform support only: N-3.
  • Preview: early validation only.
  • LTS: explicit Premium-tier support plan for eligible versions.

What to review every cycle

  • Current cluster version and latest patch.
  • Available upgrades in the cluster's region.
  • Upcoming minor-version retirement dates.
  • Whether the cluster should stay on community support or opt into LTS.
  • Whether controllers, CRDs, and node image posture still match the target version.

Useful checks

az aks show \
    --resource-group "$RG" \
    --name "$CLUSTER_NAME" \
    --query "{currentVersion:currentKubernetesVersion,supportPlan:supportPlan,autoUpgradeProfile:autoUpgradeProfile}" \
    --output yaml

az aks get-upgrades \
    --resource-group "$RG" \
    --name "$CLUSTER_NAME" \
    --output table

az aks get-versions \
    --location "$LOCATION" \
    --output table
Command Purpose
az aks show Show the current version and support plan.
--resource-group Resource group that contains the AKS cluster.
--name Name of the AKS cluster.
--query Selects version, support plan, and upgrade profile.
--output Output format for the result.
az aks get-upgrades List available upgrade versions for the cluster.
--resource-group Resource group that contains the AKS cluster.
--name Name of the AKS cluster.
--output Output format for the result.
az aks get-versions List Kubernetes versions available in the region.
--location Azure region to query.
--output Output format for the result.

Usage Notes

  • The operational target is not merely “supported”; it is “supported with enough runway left to schedule safely.”
  • Use the AKS Version Lifecycle page for conceptual differences between preview, GA, platform support, and LTS.
  • Use the AKS release tracker to verify whether a target patch or node image is available in your region before scheduling production work.
  • If you opt into LTS, keep the patch auto-upgrade channel in scope so the cluster stays on a supported patch line.

See Also

Sources