Setting the file. One moment.
Subchapter 33.7
references/optional-aks-operations.mdMarkdown3 KBView on GitHub
The base Azure plugin owns AKS recommendation, Day-0 planning, cluster setup,
application deployment, readiness, and basic operations. The sibling
aks-skills plugin is optional and contains focused, deeper operational
workflows.
aks- name prefix.Installation consent does not approve resource mutation, packet capture, or other execution. Apply each focused skill’s own approval gates separately.
| Skill | Use only when |
|---|---|
aks-troubleshooting | The customer has a live AKS incident in any scope, including workload crashes, node, networking, ingress, upgrade, or scaling problems, that benefits from deeper target-bound investigation. An application-level cause does not exclude an AKS workload incident. |
aks-known-issues | The supplied or retrieved failure includes an exact, fully qualified catalog signature. A quota error, unqualified capacity symptom, or incomplete wrapper is not enough; an exact fully qualified catalog capacity signature remains eligible. |
aks-network-capture | The customer explicitly requests and separately approves a packet capture (pcap) workflow. Generic connectivity troubleshooting stays in baseline diagnostics. |
aks-gpu-inference | An existing AKS GPU or inference deployment has a Day-2 incident. Initial GPU cluster, provider, or model setup stays with the base setup workflow. |
aks-cost-optimization | An existing cluster needs deep NAP readiness, node-pool bin-packing, constraint-driven scale-out or blocked scale-down analysis, or PVC/PV-to-Azure storage optimization. Route billed spend and anomalies to cost-analysis; route Reservations, Savings Plans, purchases, and renewals to cost-optimization, which may invoke aks-cost-optimization for AKS commitment-demand evidence. |