AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

aks-troubleshooting

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 stay here only for AKS.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--aks-troubleshooting at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 18

references/command-flows.md

AKS Command Flows

Cluster Baseline Flow

Resolve subscription -> resolve resource group -> resolve cluster -> inspect cluster state -> inspect node pools -> inspect resource health -> inspect recent operations

Portable target-bound fallback for cluster metadata and Kubernetes state:

AKS_SUBSCRIPTION_ID=<subscription-id> \
  scripts/cluster-snapshot.sh <resource-group> <cluster-name> <kube-context>

Gather resource health and recent Azure operations before this Kubernetes phase.

Kubernetes Baseline Flow

Check API reachability -> inspect nodes -> inspect kube-system -> inspect events -> inspect affected namespace -> inspect pod details and logs

The snapshot verifies the kube endpoint before any Kubernetes API read. Use the pod collector for the final pod-detail/log phase:

AKS_SUBSCRIPTION_ID=<subscription-id> \
  scripts/pod-deep-dive.sh \
  <namespace> <pod-name> <resource-group> <cluster-name> <kube-context> \
  <artifacts-directory>

Connectivity Flow

pod -> service -> endpoints -> ingress or load balancer -> DNS -> network controls

Portable Kubernetes CLI flow:

kubectl get pods -n <namespace> -o wide
kubectl get svc -n <namespace>
kubectl get endpoints -n <namespace>
kubectl get ingress -n <namespace>
kubectl describe ingress <ingress-name> -n <namespace>

Detector Flow

Use the separately advertised Azure MCP AppLens area when available; this is not part of the Azure MCP AKS metadata area.

resolve cluster resource ID -> list detectors or choose category -> select a focused time window -> run the detector or category -> rank critical findings above warnings -> ignore emerging issues when choosing the primary root cause

Monitoring Flow

Use separately advertised Azure MCP Monitor and Resource Health areas when available, or their Azure CLI equivalents.

check resource health -> inspect metrics -> verify diagnostics settings -> inspect control plane logs if available -> correlate with Application Insights or namespace symptoms

Scheduling Flow

pod events -> node capacity -> taints and tolerations -> affinity rules -> PVC state -> quotas

Portable Kubernetes CLI flow:

kubectl describe pod <pod-name> -n <namespace>
kubectl get nodes -o wide
kubectl describe node <node-name>
kubectl get pvc -n <namespace>
kubectl describe quota -n <namespace>

Deep Diagnostics Flow (Inspektor Gadget)

Standard diagnostics inconclusive -> prove the AKS/kube target -> select one symptom-specific gadget -> obtain privileged-debug approval -> run the digest-pinned command with finite bounds -> clean up the exact debug pod -> correlate output with prior evidence

Use when the standard checks relevant to the symptom do not reveal root cause; collect Azure-side, Kubernetes-side, or detector evidence as the investigation requires, not in a mandatory cross-platform sequence. See inspektor-gadget.md for the pinned command pattern and gadget catalog.

Safety Boundary

Treat the following as change operations and avoid them unless the user explicitly asks for remediation:

  • deleting or restarting pods
  • cordon and drain operations
  • scaling workloads or node pools
  • cluster upgrade operations
  • DNS, route, NSG, or firewall changes