What problem does it solve? Deploying applications to cloud Kubernetes clusters (AKS, GKE, DOKS) involves recurring pitfalls: architecture mismatches between build platform and cluster nodes, Next.js build-time versus runtime environment variables, Helm comma-parsing errors, and opaque ImagePullBackOff or CrashLoopBackOff failures. This Skill provides a structured deployment workflow and troubleshooting guide to resolve these issues systematically. ## Core Features & Use Cases - Architecture Matching: Verify cluster node architecture (arm64 vs amd64) and configure Docker buildx platforms accordingly, avoiding "no match for platform" and "exec format error" failures. - CI/CD Pipeline Setup: Configure GitHub Actions with path filters for selective builds, pass Next.js NEXT_PUBLIC_* variables as build args, and deploy via Helm with secrets passed through --set. - Troubleshooting Playbook: Diagnose ImagePullBackOff, CrashLoopBackOff, Pending pods, Helm parsing errors, and password authentication failures with concrete fixes. - Use Case: A team pushing a Next.js frontend and FastAPI backend to an arm64 AKS cluster uses this Skill to set up selective GitHub Actions builds, embed NEXT_PUBLIC_API_URL at build time, and deploy with Helm while avoiding manifest and comma-parsing errors. ## Quick Start Ask the AI to check your cluster node architecture and generate a GitHub Actions workflow that builds your Docker images for the matching platform and deploys them with Helm.
