debug-k8s

Debug Kubernetes deployment issues including pod failures and ArgoCD sync problems.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/vesviet/microservices-agent-skills --skill debug-k8s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-k8s
Source: https://github.com/vesviet/microservices-agent-skills/tree/main/skills/debug-k8s
Command: npx skills add https://github.com/vesviet/microservices-agent-skills --skill debug-k8s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and fix common problems encountered during Kubernetes deployments, ensuring services run smoothly and reliably.

Core Features & Use Cases

  • Pod Troubleshooting: Addresses issues like CrashLoopBackOff, ImagePullBackOff, and Pending states.
  • Configuration Debugging: Identifies problems with ConfigMaps, Secrets, and service definitions.
  • GitOps Workflow: Guides users through fixing issues by modifying GitOps configurations and triggering ArgoCD syncs.
  • Use Case: When a new service deployment fails to start due to a missing environment variable or an incorrect image tag, this skill provides the steps to diagnose the root cause and apply the fix through the GitOps pipeline.

Quick Start

Use the debug k8s skill to find why pods are in a CrashLoopBackOff state in the order-dev namespace.

Frequently Asked Questions about debug-k8s

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

FAQPage Schema
How do I fix a Kubernetes pod stuck in CrashLoopBackOff?

To resolve an ArgoCD synchronization failure, you modify the GitOps configurations in the repository to correct configuration errors. This Skill guides you through diagnosing sync problems and triggering ArgoCD syncs to update the deployment state.

How do I debug ConfigMaps and Secrets configuration errors in microservices?

To debug a Pending pod state in a Kubernetes deployment, you use kubectl and SSH access to diagnose resource or configuration issues. This Skill addresses Pending states by identifying the root cause and applying fixes through the GitOps repository.

Do I need kubectl and SSH access to troubleshoot Kubernetes deployments?

Yes, you need kubectl and SSH access to the development cluster to troubleshoot Kubernetes deployments. This Skill requires these access levels to diagnose pod failures and manipulate the GitOps repository for applying fixes.

What is the best way to resolve ImagePullBackOff errors in a GitOps workflow?

The best way to resolve ImagePullBackOff errors in a GitOps workflow is to correct the incorrect image tag in the GitOps configurations. This Skill provides the steps to diagnose the root cause and trigger an ArgoCD sync to apply the fix.