k8s-debugging

Diagnose Kubernetes pod, network, and cluster issues with actionable commands.

3|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/eco2-team/backend --skill k8s-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-debugging
Source: https://github.com/eco2-team/backend/tree/main/.claude/skills/k8s-debugging
Command: npx skills add https://github.com/eco2-team/backend --skill k8s-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Kubernetes environments are complex and debugging issues across pods, networks, and controllers is time consuming and error prone.

Core Features & Use Cases

  • Comprehensive pod troubleshooting, including crash loops, readiness/liveness, and log correlation.
  • Network and service mesh diagnostics: DNS checks, end-to-end tests, and Istio/Envoy tracing workflows.
  • GitOps/ArgoCD focused guidance for diagnosing deployment and rollout issues in cluster environments.
  • Use Case: When a new canary release causes intermittent failures, follow this guide to isolate the failing component and restore service quickly.

Quick Start

Use this skill to triage a failing chat-api pod by listing pods, checking status, and viewing logs.

Frequently Asked Questions about k8s-debugging

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

FAQPage Schema
How do I troubleshoot a Kubernetes pod stuck in a crash loop?

To troubleshoot a Kubernetes pod crash loop, you need to list pods, check status conditions, and correlate logs. This skill provides actionable commands to isolate the failing component and resolve readiness or liveness probe failures quickly.

What is the best way to diagnose Kubernetes networking and DNS issues?

Diagnosing Kubernetes networking issues involves running DNS checks and end-to-end connectivity tests. This skill guides operators through network diagnosis procedures, including Istio and Envoy tracing workflows, to identify and resolve service mesh routing failures.

How do I debug ArgoCD deployment and rollout failures in Kubernetes?

Debugging ArgoCD deployment failures in Kubernetes requires diagnosing GitOps workflows and cluster topology. This skill offers targeted guidance to identify rollout issues, check controller states, and restore service during intermittent canary release failures.

Can I use this Kubernetes debugging guidance directly in production environments?

Yes, you can use this Kubernetes debugging guidance directly in production environments. The skill is self-contained with actionable commands and references designed to help operators triage failing pods and resolve issues safely without additional setup.

Why does my Kubernetes canary release cause intermittent failures?

Intermittent canary release failures usually stem from misconfigured routing or pod instability within the cluster topology. This skill helps you isolate the failing component by analyzing logs, checking Istio routing, and performing end-to-end network diagnostics.

How do I analyze Istio and Envoy routing issues in a service mesh?

Analyzing Istio and Envoy routing issues requires tracing request flows across the service mesh. This skill provides network diagnosis workflows to check DNS, trace Envoy configurations, and identify routing anomalies affecting cluster communication.