AKS in 2026: Automatic, Workload Identity, and the Cluster You Actually WantOfficial sources14 of 14 sources come from the companies and standards bodies that own the technology.This rates where the sources come from. It doesn't prove every claim.
AKS Automatic vs Standard, Azure CNI Overlay + Cilium, Workload Identity (Pod Identity is dead), Node Auto Provisioning, and a sane upgrade strategy.
By Amit UpadhyayPublished Updated 15 minArticle 4 of 7 in Cloud (Azure)
AI assistant · answers from this article
1 of 6
A development cluster
Nothing to add yet
For development the defaults are fine, and AKS Automatic gives you sensible ones without choosing.
On this page
Azure Kubernetes Service, in one sentence
AKS runs the Kubernetes control plane for you, and how your workloads behave during an upgrade or a busy hour still depends on what you declare about them.
You reach for it when several containerised services run on a managed Kubernetes cluster. Not before: it costs configuration per service, and slightly more nodes so replicas can spread.
The cheat sheet
What to use when
You do not need all of this on day one. Each row is one signal and the piece that answers it. Stop at the row your system has reached, or pick one to see it in the picture above.
Where you areThe signalWhat to useWhat it costs
None. Nothing depends on it staying up.Nothing. The defaultsNothing
One hungry pod starves its neighbours, because nothing declares what any of them needs.CPU and memory requests on every containerCost and requests ↓Measuring before you set them
A monthly node-image upgrade takes checkout down, because every replica was evicted at once.PodDisruptionBudgets, and replicas spread across nodes and zonesHow clusters get into trouble ↓Drains that wait
Cluster DNS shares nodes with a busy application, and name lookups start to fail.A dedicated system node poolHow clusters get into trouble ↓A small pool to pay for
Connection strings sit in Kubernetes Secrets, or the cluster still relies on the retired pod identity.Workload Identity, federated to a managed identity for each workloadStep 3 ↓A federation to set up for every workload
The cluster has skipped several minor versions and cannot upgrade in one hop.The stable auto-upgrade channel, with a maintenance windowStep 6 ↓Workloads that have to tolerate an upgrade
Start With the Defaults in Dev
For a development cluster, the defaults are fine, and AKS Automatic gives you sensible ones without choosing. The settings below matter once real services share the cluster, because Kubernetes can only plan with what you tell it.
Take a typical case, made up for illustration. A monthly node-image upgrade took a store's checkout down for six minutes. Nothing was wrong with the upgrade. Both checkout replicas just happened to be on the same node, there was no disruption budget, and the drain evicted them together. The same cluster had pods with no resource requests, so when nodes overloaded, the autoscaler saw nothing to do.
AKS takes the control plane off your hands, and that is a big deal. What it cannot do is guess how your workloads should be scheduled, spread, protected and authenticated. Below is the cluster shape I would build today: node pools, requests and limits, disruption budgets, Workload Identity, networking choices, and what AKS Automatic sets up for you.
If routine upgrades make you nervous
You stood up an AKS cluster from the portal three years ago and haven't upgraded since
You don't know the difference between AKS Standard and AKS Automatic
You're still using AAD Pod Identity (deprecated) and don't know how to migrate to Workload Identity
Your cluster has a public API server because "it was easier"
Pro deep dive15 min full read
Keep reading with Pro
This is one of our advanced production deep dives. Pro unlocks the rest of it, every other deep dive, and the See, Animate, Test and Build modes on every topic.
What it covers
AKS Automatic vs Standard, Azure CNI Overlay + Cilium, Workload Identity (Pod Identity is dead), Node Auto Provisioning, and a sane upgrade strategy.