AGENTIC MEMORY

Skills

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

← Back to Skills

azure-diagnostics

Debug Azure production issues using AppLens, Azure Monitor, resource health, and safe triage, including evidence-only diagnosis without live access. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

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--azure-diagnostics 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 · 42

troubleshooting/aks/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.