arc-runner-troubleshooting

What problem does it solve?

Self-hosted GitHub Actions runners (ARC) on Kubernetes can suffer from stuck jobs, scaling issues, and configuration mismatches, leading to CI/CD bottlenecks and developer frustration. This Skill provides a structured approach to diagnose and resolve these critical issues.

Core Features & Use Cases

• Empty Labels Diagnosis: Pinpoints the critical releaseName vs runnerScaleSetName mismatch causing runners to register with no labels.
• Queued Job Resolution: Identifies and fixes cold-start delays due to minRunners: 0 configurations.
• Cluster Access & Kubeconfig Fixes: Guides through resolving expired kubeconfig tokens and DNS failures.
• Custom Runner Image Validation: Ensures the correct runner image with pre-installed tools is used.
• Use Case: When your GitHub Actions workflows are stuck in a "queued" state for an extended period, activate this Skill to quickly identify if it's an empty label issue, a cold-start delay, or a cluster access problem, and get step-by-step instructions to fix it.

Quick Start

Use the arc-runner-troubleshooting skill to diagnose why GitHub Actions jobs are stuck in the 'queued' state for the 'project-beta-api' repository. Provide a checklist of steps to investigate and potential fixes.