devops:k8s-troubleshoot

Diagnose Kubernetes pod and cluster issues with root cause analysis.

Updated Feb 27, 2026

Search Tags:#devops #troubleshooting #kubernetes #RCA #cluster management #k8s events #pod errors

Ready to run

npx skills add https://github.com/ChanghwanK/dotfiles --skill devops-k8s-troubleshoot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devops:k8s-troubleshoot
Source: https://github.com/ChanghwanK/dotfiles/tree/main/claude/.claude/skills/devops%3Ak8s-troubleshoot
Command: npx skills add https://github.com/ChanghwanK/dotfiles --skill devops-k8s-troubleshoot

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you diagnose and resolve complex issues within Kubernetes clusters, from Pod lifecycle errors to cluster-wide infrastructure problems, and design plans to prevent recurrence.

Core Features & Use Cases

Root Cause Analysis (RCA): Systematically identify the underlying causes of Kubernetes failures.
Troubleshooting: Analyze Pod errors (CrashLoopBackOff, OOMKilled), cluster events, and infrastructure alerts.
Improvement Planning: Design actionable plans to enhance cluster stability and prevent future incidents.
Use Case: When a critical service's Pods are stuck in CrashLoopBackOff, this Skill can analyze logs, events, and resource metrics to pinpoint the exact cause (e.g., configuration error, resource limit) and suggest a fix.

Quick Start

Use the devops:k8s-troubleshoot skill to diagnose why pods are in a CrashLoopBackOff state in the staging namespace.

Frequently Asked Questions about devops:k8s-troubleshoot

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

FAQPage Schema

How do I troubleshoot Kubernetes pods stuck in CrashLoopBackOff?▼

Troubleshoot CrashLoopBackOff by analyzing Kubernetes events, pod logs, and resource metrics to identify the root cause. This skill pinpoints exact failures like configuration errors or resource limits and suggests actionable remediation strategies.

Why are my Kubernetes pods in Pending state and how do I fix it?▼

Diagnose Pending state in Kubernetes by correlating cluster events and infrastructure metrics to find scheduling failures or resource shortages. The skill performs root cause analysis to determine if scheduler failures or node issues are blocking deployment.

How do I perform root cause analysis for Kubernetes node issues?▼

Perform root cause analysis for Kubernetes node issues by examining cluster events, API server overload indicators, and etcd delays. This skill correlates infrastructure alerts to identify underlying problems and designs improvement plans to prevent recurrence.

What is the best way to diagnose OOMKilled errors in EKS clusters?▼

Diagnose OOMKilled errors in EKS by analyzing pod resource limits and correlating metrics from Kubernetes events. This skill identifies memory exhaustion as the root cause and provides remediation strategies to adjust allocations and stabilize services.

Can I use this skill to troubleshoot API server overload and etcd delays?▼

Yes, you can troubleshoot API server overload and etcd delays by analyzing cluster-wide infrastructure events. The skill diagnoses these control plane issues, performs root cause analysis, and designs actionable plans to enhance cluster stability.

How do I resolve ImagePullBackOff errors in my Kubernetes cluster?▼

Resolve ImagePullBackOff by analyzing Kubernetes events to identify image registry or configuration issues. This skill performs root cause analysis on the pod lifecycle error and provides specific remediation strategies to correct the deployment.