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

spot-and-zone-issues.md

Spot And Zone Issues

Use this guide when workload placement, evictions, or zonal behavior is causing node-pool instability.

Spot Node Pool Evictions

AKS spot nodes use Azure Spot VMs - they can be evicted with 30 seconds notice when Azure needs capacity.

Diagnose spot eviction:

# Spot nodes carry this taint automatically
kubectl describe node <node> | grep "Taint"
# kubernetes.azure.com/scalesetpriority=spot:NoSchedule

# Check eviction events
kubectl get events -A --field-selector reason=SpotEviction
kubectl get events -A | grep -i "evict\|spot\|preempt"

Spot workload pattern: pods must tolerate the spot taint. Prefer PDBs and avoid stateful PVC workloads on spot.

tolerations:
  - key: "kubernetes.azure.com/scalesetpriority"
    operator: Equal
    value: spot
    effect: NoSchedule

Add this preferred node affinity when you want the workload to bias toward spot nodes:

affinity:
  nodeAffinity:
    preferredDuringSchedulingIgnoredDuringExecution:
      - weight: 1
        preference:
          matchExpressions:
            - key: kubernetes.azure.com/scalesetpriority
              operator: In
              values: ["spot"]

Multi-AZ Node Pool & Zone-Related Failures

Check zone distribution:

kubectl get nodes -L topology.kubernetes.io/zone

Zone-related failure patterns:

| Symptom | Cause | Fix | | ------------------------------------------------ | ---------------------------------------------------- | ------------------------------------------------------------ | | Pods stack on one zone after node failures | Scheduling imbalance after zone failure | kubectl rollout restart deployment/<n> to rebalance | | PVC pending with volume node affinity conflict | Azure Disk is zonal; pod scheduled in different zone | Use ZRS storage class or ensure PVC and pod are in same zone | | Service endpoints unreachable from one zone | Topology-aware routing misconfigured | Check service.spec.trafficDistribution or TopologyKeys | | Upgrade causing zone imbalance | Surge nodes in one zone | Configure maxSurge in node pool upgrade settings |

Use Premium_ZRS or StandardSSD_ZRS in custom StorageClasses to reduce zonal PVC conflicts. See AKS storage best practices.