k8s-aks-troubleshooting
AKS troubleshooting
Find out why something that depends on Azure fails in an AKS cluster, and propose a fix.
Read first, ask before changing. Run the investigation commands freely: kubectl reads
and the read-only az commands below (show, list, get). Run a command under an "Ask
first" line only after the user approves that exact command; if your credentials do not
allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user.
Every az change (update, upgrade, role assignments, anything that writes) is a proposed
fix.
An AKS cluster lives in two places. Kubernetes objects are in the cluster; the cluster
itself, its node pools (virtual machine scale sets), load balancers, public IPs, disks
and identities are Azure resources. The cluster resource is in the user's resource group;
the resources AKS manages for it are in a separate node resource group (by default
MC_<resource group>_<cluster>_<region>). Many AKS failures show in Kubernetes only as a
short event, while the real error is in Azure: in the cluster's provisioningState, in
the latest operation, or in the activity log.