# Aks Troubleshooting

> Triage AKS symptoms safely with read-only evidence and an escalation boundary.

- Skill: `prashantyr/aks-troubleshooting` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add prashantyr/aks-troubleshooting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/prashantyr/aks-troubleshooting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: prashantyr (https://skillmd.com/u/prashantyr)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/prashantyr/aks-troubleshooting

---


# AKS Troubleshooting

Use for AKS connectivity, scheduling, networking, DNS, upgrade, or workload-identity symptoms.

1. Establish subscription, cluster, namespace, time window, and user impact without requesting keys.
2. Start with Azure Resource Health and read-only commands (`az aks show`, `kubectl get`,
   `kubectl describe`, and bounded `kubectl logs`). Confirm context before every cluster command.
3. Classify evidence into control plane, node, network/DNS, identity, storage, or workload.
4. Run `python aks-troubleshooting/scripts/check_manifest.py <manifest.yaml>` for a conservative
   static signal. It does not parse credentials, contact Azure, or mutate resources.
5. Present evidence, confidence, and the smallest reversible remediation. Obtain explicit approval
   before restarts, scaling, upgrades, role changes, or policy changes.

Never print kubeconfig/client secrets, run broad log collection without scoping, disable policy,
change production resources, or use `--admin` by default. Provider-backed explanations are optional;
use local Ollama first and redact identifiers before any commercial provider.