3.2k microsoft

aks-gpu-inference Skill

使用基于配置画像的只读证据来诊断 AKS GPU 和 KAITO 的 Day-2 故障。适用场景:“Insufficient nvidia.com/gpu”、GPU Pod Pending、模型加载 OOM、DCGM/显存、KAITO Workspace 未就绪或 GPU 自动扩缩容。不适用于:环境搭建(airunway-aks-setup)、非 GPU 故障(aks-troubleshooting)、独立 VM 配额(azure-quotas)或一般成本分析(可选 azure-cost 插件的 cost-analysis 或 cost-optimization)。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

AKS GPU Inference Day-2

Quick Reference

| Property | Value |
|---|---|
| Best for | AKS GPU/KAITO failures |
| Evidence | Bound target, events/status, gpuProfile, DCGM |

When to Use This Skill

Use for scheduling, VRAM/OOM, KAITO readiness, and workload scaling. Route
exclusions as described above.

MCP Tools

Use a fitting host-advertised Azure read or the references' read-only queries.

Host Capability Gate

Before executing any referenced pipeline, verify that the host authorizes
the required shell and kubectl/az commands against the bound target.
File-backed collection also requires approved artifact storage and access to
any bundled files it uses. A governed Azure CLI tool alone does not establish
these capabilities. Equivalent host reads may replace commands only where
their advertised schemas provide the required evidence.

If execution is unavailable or prohibited, say so and analyze supplied or
redacted events, status, logs, and metrics, or give the operator a scoped
collection plan. State which reads did not run and leave conclusions requiring
missing evidence unconfirmed. Never route kubectl through Azure MCP or
bypass host policy. The authorization requirements below still apply.

Workflow

  1. Bind subscription, cluster, kube context, pool, and affected resource.
  2. Capture exact events/status and observed gpuProfile; state which reads ran.
  3. Route to scheduling,

observability,
KAITO, or
scaling.

  1. Separate container/host OOM from device-allocation failures. For OOMKilled,

correlate container memory limits/usage and node conditions. For
Managed+Install device-memory evidence, use the exporter on port 19400 and
incident-window FB_USED/FB_FREE; sizing tables do not establish a cause.

  1. For KAITO not-ready, warn that Workspace deletion leaves its GPU pools;

cleanup is separate and needs explicit authorization.

  1. Report evidence, confidence, missing evidence, and owner handoff.

Require explicit authorization before scaling, cordon/drain, deletion,
add-on enablement, or monitoring mutation.

Error Handling

| Condition | Response |
|---|---|
| Missing/contradictory evidence | Mark unconfirmed; request the owner/read |
| Unknown profile | Preserve evidence; do not prescribe stack repair |
| Mutation required | Propose separately and wait for authorization |