How does this skill help with Kubernetes incidents?

It provides a structured, multi-phase methodology to investigate failures, ensuring you check events, logs, and metrics in the correct order to identify the actual root cause rather than just symptoms.

Can it fix my Kubernetes issues automatically?

No, this skill follows a 'Read-Only Investigation' principle to ensure cluster safety. It provides detailed remediation plans and manual recommendations that you can review and apply.

What common K8s errors does this skill cover?

It includes specialized logic for ImagePullBackOff, Pending pods, CrashLoopBackOff, OOMKilled events, and TLS/certificate failures.

Does it work with cloud-managed Kubernetes?

Yes, the investigation methodology is environment-agnostic and works across EKS, GKE, AKS, and on-premise Kubernetes clusters.

Kubernetes Incident Debugging

Name: Kubernetes Incident Debugging
Author: geored

bygeored

Despliegue y DevOps

Guides systematic investigation and root cause analysis of Kubernetes pod failures and service degradations.

Acerca de

This skill equips Claude Code with a structured SRE methodology for troubleshooting complex Kubernetes environments. It provides a comprehensive framework for incident triage, multi-source data collection, and temporal correlation of logs, events, and metrics. By following five distinct investigation phases, the skill helps identify the underlying root cause of common issues like CrashLoopBackOff, OOMKilled events, and TLS failures while adhering to safety-first, read-only investigation principles.

Características Principales

Previous container log analysis for transient failure investigation
Structured remediation planning including immediate mitigation and prevention
0 GitHub stars
Systematic 5-phase investigation methodology (Triage to Remediation)
Targeted decision trees for OOMKilled, Pending, and CrashLoopBackOff states
Multi-source correlation of logs, events, and resource metrics

Casos de Uso

Diagnosing production pods stuck in CrashLoopBackOff or Pending states
Investigating resource exhaustion and memory leaks (OOMKilled)
Troubleshooting service-level connectivity and TLS certificate issues

Acerca de

Características Principales

Previous container log analysis for transient failure investigation
Structured remediation planning including immediate mitigation and prevention
0 GitHub stars
Systematic 5-phase investigation methodology (Triage to Remediation)
Targeted decision trees for OOMKilled, Pending, and CrashLoopBackOff states
Multi-source correlation of logs, events, and resource metrics

Casos de Uso

Diagnosing production pods stuck in CrashLoopBackOff or Pending states
Investigating resource exhaustion and memory leaks (OOMKilled)
Troubleshooting service-level connectivity and TLS certificate issues