aks-deployment-troubleshooter

Diagnose AKS deployment failures using kubectl and helm checks.

27|11|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/mjunaidca/mjs-agent-skills --skill aks-deployment-troubleshooter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aks-deployment-troubleshooter
Source: https://github.com/mjunaidca/mjs-agent-skills/tree/main/docs/taskflow-vault/skills/engineering/aks-deployment-troubleshooter
Command: npx skills add https://github.com/mjunaidca/mjs-agent-skills --skill aks-deployment-troubleshooter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix AKS deployment failures with a structured, battle-tested flow addressing 10+ failure modes.

Core Features & Use Cases

  • Diagnosis Flow: Step-by-step checks from Pod status to node architecture
  • Common Failures: ImagePullBackOff, CrashLoopBackOff, and platform mismatches
  • Guided Resolutions: Commands and remedies to fix failures quickly

Quick Start

Follow the diagnostic steps when a pod fails, starting with Pod status and logs.

Frequently Asked Questions about aks-deployment-troubleshooter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose ImagePullBackOff errors in AKS deployments?

ImagePullBackOff occurs when a pod cannot pull its container image from a registry. Check pod status with kubectl, verify registry credentials and secrets are configured, confirm the image URI is correct, and ensure the node can reach the registry endpoint. The diagnostic flow identifies authentication failures, invalid image references, or network connectivity issues.

What causes CrashLoopBackOff with exec format errors in Kubernetes?

CrashLoopBackOff with exec format errors typically means the container image architecture doesn't match the node's processor architecture—for example, running an ARM image on an x86 node. Verify node architecture, check the image manifest for platform support, and redeploy with a compatible image build or add multi-architecture image layers to your Helm chart.

How do I troubleshoot 'no match for platform' errors in AKS?

Platform mismatch errors occur when a container image lacks support for your node's architecture. Inspect the image manifest using registry tools, confirm your AKS node pool's processor type, and either rebuild the image for that platform or use a multi-architecture image. The workflow guides kubectl and helm commands to verify and resolve the mismatch.

Can I use kubectl and Helm to diagnose AKS deployment failures?

Yes. The diagnostic workflow uses kubectl to inspect pod status, events, and logs, and helm to check deployment timeouts and configuration. Combined with registry secret checks, these tools form a structured process to identify root causes across image pull, crash loop, and architecture failure modes without requiring external monitoring tools.

What should I check first when a pod fails in AKS?

Start by checking pod status and recent events with kubectl describe pod, then review container logs for startup errors. This reveals whether the failure is in image pull, container execution, or application startup. The diagnostic flow prioritizes these steps to quickly narrow the root cause—image access, compatibility, or configuration.

Do I need specific Helm chart changes to fix deployment timeouts in AKS?

Helm deployment timeouts often stem from unresolved image pulls or unhealthy pods. The troubleshooter guides you to verify image availability, registry authentication, and node readiness before adjusting Helm timeout settings. Configuration adjustments and remediation steps address the underlying failure, not just the symptom.