aks-troubleshooting
以只读、证据优先的调查方式调试线上 Azure Kubernetes Service（AKS）事件。适用场景：Pod 崩溃或处于 Pending、CrashLoopBackOff、OOMKilled、ImagePullBackOff、节点 NotReady、DNS 或入口故障、连接超时、网络策略、SNAT 耗尽、节点池扩缩容因 QuotaExceeded 或 InsufficientVCPUQuota 受阻、升级卡住、Spot 或可用区中断、仅有 VMExtensionProvisioningError 或 AllocationFailed 包装的错误、未收录的容量症状，或“调查我的 AKS 集群”。不适用于：数据包捕获（使用 aks-network-capture）；GPU 或模型服务问题（使用 aks-gpu-inference）；集群创建或预配（使用 azure-kubernetes）；成本（使用可选 azure-cost 插件中的 cost-analysis）；Pod 规格调整（使用 azure-kubernetes）；带有全部必需嵌套限定符的完全限定且已记录的 AKS 特征（使用 aks-known-issues）；非 AKS Azure 资源上的独立故障（使用 azure-diagnostics）。未限定的错误和开放式事件。
机器翻译查看英文原文
Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or InsufficientVCPUQuota, upgrade stuck, spot or zone disruption, a bare VMExtensionProvisioningError or AllocationFailed wrapper, an uncataloged capacity symptom, or 'investigate my AKS cluster'. DO NOT USE FOR: packet capture (use aks-network-capture); GPU or model-serving issues (use aks-gpu-inference); cluster creation or provisioning (use azure-kubernetes); cost (use cost-analysis from the optional azure-cost plugin); pod rightsizing (use azure-kubernetes); a fully qualified documented AKS signature with every required nested qualifier (use aks-known-issues); standalone failures on non-AKS Azure resources (use azure-diagnostics). Unqualified errors and open-ended incidents
适用对象：软件开发与测试。自动收录 · 待核查。
原作者说明节选
从固定版本的 SKILL.md 提取，保留原文语言。以下内容属于作者说明，本站尚未验证安装、兼容或运行结果。
查看英文原文
原文涵盖的主题
- 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
这里只展示节选，请以完整原文和当前要求为准。
- 来源仓库
- microsoft/skills
- 源文件
- .github/plugins/aks-skills/skills/aks-troubleshooting/SKILL.md
- 固定版本
- 9287b443662d2433c85621c7325ee72a0ce499b5
来源与内容状态
本条为自动发现的元数据，尚未完成人工文档核查；适用性与运行结果待核查。
原作者：Microsoft Skills · 原作者仓库元数据。文档核查：未核查。最近来源检查：2026-11-10T19:02:05.878Z。
分类由名称、说明与路径规则生成，分类不代表已核实适配。
许可与权利归属
MIT。第三方内容及版权归原作者，使用条件以原文为准。
许可原文 ↗本站没有因同步、复制或用户自报成功而将资源标为运行验证通过。
限制与注意事项
- 元数据收录不代表本站已经安装、适配、实测或进行安全审查。