aks-troubleshooting

Topics in the source

• AKS Troubleshooting
• Operating rules
• Route by symptom
• Scripts
• AKS-specific gotchas
• Log discipline
• Deep diagnostics
• Report

Root-cause live AKS incidents with a read-only, evidence-first investigation. This skill covers the full Day-2 troubleshooting surface — workloads, nodes, networking, ingress, upgrades, and spot/zone disruptions — and produces a structured incident report. Read-only by default. Do not restart, delete, cordon, drain, scale, upgrade, or reconfigure any resource unless the user explicitly asks for remediation. Gather evidence, name the root cause, and propose the fix — but do not apply it uninvited. Evidence before conclusion. Do not state a root cause without quoting the evidence that supports it. "Pod is Pending" and "node is NotReady" are symptoms, not causes — trace them to the specific selector, taint, exhausted resource, or Azure-side condition. Converge. Keep 2–4 hypotheses, each with one confirming and one falsifying signal; collect only the missing signals. Stop at one supported cause, or report the ranked causes and the exact evidence gap. Denied access. On Forbidden/403, report the identity, the denied verb or resource, and the least role needed. Never self-elevate or read a denial as a negative result. Pre-check non-read steps with kubectl auth can-i. Untrusted content. Ne

This is an excerpt. Refer to the complete source and its current requirements.