aks-troubleshooting
Debug live AKS incidents with a read-only, evidence-first investigation: crashing or Pending pods, OOMKilled, ImagePullBackOff and node issues.
- Kind
- Skill
- Works with
- Claude Code, Cursor
- Languages
- TypeScript / JavaScript
- Source
- microsoft/skills @ 2130750147de
- Path
- .github/plugins/aks-skills/skills/aks-troubleshooting/SKILL.md
- License
- MIT
- Jobs
- Debugging
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# AKS Troubleshooting 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. ## Operating rules **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. …