Azure Kubernetes Service added public preview support for Ubuntu 26.04 on September 30, 2026, through a new versioned OS SKU called Ubuntu2604. The SKU is built on Ubuntu Minimal rather than the standard Ubuntu Server image, which changes what lands on your nodes before a single container starts. Anyone who manages Ubuntu node pools should understand what this preview offers and what it deliberately leaves out.
What the Ubuntu2604 SKU actually requires
This is a preview with real gates, not just a label flip. According to the AKS OS version upgrade documentation, the SKU is supported only on Kubernetes 1.36 and later, and you have to register the Ubuntu2604Preview feature flag before you can use it. The preview also requires Azure CLI 21.0.0b14 or later, so teams pinned to older CLI versions will need to upgrade their tooling first.
The hardware requirements matter too. Ubuntu 26.04 node images are minimal images for both AMD64 and Arm64, and they require a VM size capable of running Generation 2 VMs. Three things are explicitly unsupported while the SKU is in preview: FIPS compliance, Confidential VMs, and Trusted Launch. If any of your node pools depend on those, this preview is not for them yet, and there is no announced date for when they arrive.
Why Ubuntu Minimal changes the picture
The interesting engineering decision here is the move to Ubuntu Minimal as the base. Canonical’s own documentation on Minimal Ubuntu describes images that are less than half the size of the standard server image and boot up to 40 percent faster, achieved by stripping editors, documentation, locales, and other tooling that Kubernetes nodes rarely need.
For a node pool, a smaller package footprint means fewer packages to patch each cycle and a smaller attack surface sitting underneath your workloads. The tradeoff is on the debugging side: anything in your node bootstrap scripts or troubleshooting runbooks that expects man pages, editors, or standard locale data will find them missing. Teams that customize nodes heavily should test those workflows against the minimal image before committing production pools.
How the default Ubuntu SKU tracks Kubernetes
To see why this SKU exists, look at how AKS maps Ubuntu releases to Kubernetes versions. The default Ubuntu SKU pairs Ubuntu 22.04 with Kubernetes 1.25 through 1.34, and Ubuntu 24.04 with Kubernetes 1.35 and later. Clusters on the default SKU migrate to 24.04 automatically when they upgrade to Kubernetes 1.35 or higher, which is convenient but gives you no control over timing. The versioned SKUs, including Ubuntu2204 and Ubuntu2404, exist so teams can pin or migrate an OS deliberately rather than inherit one from a Kubernetes upgrade.
Ubuntu2604 follows that same versioned pattern. Adopting it is a manual decision, which means you can evaluate 26.04 on a staging pool while production stays on 24.04. It also means you own the migration schedule instead of having it ride along with a Kubernetes version bump.
Migrating a node pool in place
Existing pools move to the new SKU with az aks nodepool update and the --os-sku Ubuntu2604 flag, without requiring a Kubernetes version upgrade. Under the hood, the change follows the standard node image upgrade cycle: surge nodes come up, existing nodes are cordoned and drained, then reimaged on the new OS. The default max surge is one extra node, though Microsoft recommends 33 percent for production pools to keep the rollout moving. Before migrating, check that your subnet has IP headroom for the surge nodes and that your quota supports the temporary capacity.
If the preview misbehaves, the fallback is to move the pool back to Ubuntu2404, which is supported on Kubernetes 1.32 through 1.38. That gives a supported rollback window during the preview period rather than a dead end.
The retirement clock is the real driver
The timing is not accidental. AKS ends support and security updates for Ubuntu 22.04 on June 30, 2027, and removes Ubuntu 22.04 node images on April 30, 2028. After image removal, scaling and remediation operations on 22.04 pools fail, which turns an old OS into an outage risk rather than a mild inconvenience. The AKS node images documentation also notes that AKS will not retire an Ubuntu version before Canonical’s own support lifecycle ends, but the 2027 date is now less than nine months away.
For teams still on 22.04, this preview is a preview of the exit path. The default SKU migration to 24.04 will handle most clusters automatically at Kubernetes 1.35, but 26.04 is where the platform is heading next, and the minimal image is the shape of future node images.
What to do this week
If you run Ubuntu node pools on AKS, the practical moves are straightforward. Register the Ubuntu2604Preview flag and upgrade your Azure CLI to 21.0.0b14 or later. Stand up a non-production node pool with the Ubuntu2604 SKU and run your application compatibility checks against it, paying attention to anything in node bootstrap scripts that expects standard Ubuntu tooling. Confirm your target VM sizes support Generation 2. Audit which pools still run Ubuntu 22.04 and schedule their migrations well ahead of the June 2027 cutoff. And set max surge to 33 percent on production pools before you start any OS migration, because the default of one surge node makes for a slow rollout on large pools.
The preview period is the cheap time to find out whether Ubuntu Minimal breaks anything you depend on. Teams that wait until general availability will be migrating under the retirement deadline instead.