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"