kubernetes-debug

Diagnose Kubernetes pod issues using events, logs, and pod descriptions.

654|77|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/incidentfox/incidentfox --skill kubernetes-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubernetes-debug
Source: https://github.com/incidentfox/incidentfox/tree/main/sre-agent/.claude/skills/infrastructure-kubernetes
Command: npx skills add https://github.com/incidentfox/incidentfox --skill kubernetes-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubernetes, and includes scripts (resource) components.

What problem does it solve?

Kubernetes debugging is often time-consuming due to scattered signals from events, pod status, and containers. This Skill provides a repeatable methodology and a set of scripts to quickly surface the root cause of pod issues in Kubernetes clusters.

Core Features & Use Cases

  • Event-first debugging: Start with pod events to identify scheduling or runtime issues before diving into logs.
  • Pod visibility: List pods in a namespace with status, ready state, and restart info to identify candidates for investigation.
  • Evidence gathering: Retrieve events, describe pods, and fetch logs to build a concise incident timeline.
  • Use Case: When a pod shows CrashLoopBackOff or ImagePullBackOff, run the scripts to surface root causes and recommended remediation steps.
  • Extensibility: Works with additional kubectl/kubernetes tooling and can be extended with new scripts under scripts/.

Quick Start

Start by listing pods in your target namespace, then inspect the failing pod with events and logs:

  • python .claude/skills/infrastructure-kubernetes/scripts/list_pods.py -n <namespace>
  • python .claude/skills/infrastructure-kubernetes/scripts/get_events.py <pod-name> -n <namespace>
  • python .claude/skills/infrastructure-kubernetes/scripts/get_logs.py <pod-name> -n <namespace>

Frequently Asked Questions about kubernetes-debug

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

FAQPage Schema
How do I debug Kubernetes pods stuck in CrashLoopBackOff or ImagePullBackOff?

To debug Kubernetes pods in CrashLoopBackOff or ImagePullBackOff, use event-first debugging to surface scheduling or runtime issues, then fetch pod descriptions and logs to identify the root cause and remediate.

What is the best way to investigate Kubernetes pod readiness failures and reduce MTTR?

The best way to reduce MTTR for Kubernetes pod readiness failures is to follow a repeatable debugging methodology that lists pods, retrieves events, describes pod status, and fetches logs to build a concise incident timeline.

How do I list Kubernetes pods with status and restart info in a specific namespace?

You can list Kubernetes pods in a specific namespace by running a Python script that surfaces pod status, ready state, and restart counts, helping you quickly identify candidate pods for further investigation.

Do I need the kubernetes Python client library to fetch pod events and logs?

Yes, you need the kubernetes Python client library installed to run the scripts that list pods, fetch events, describe pods, and retrieve logs for debugging Kubernetes pod-level issues.

Why does my Kubernetes pod show scheduling failures even when logs look normal?

Kubernetes pod scheduling failures often appear in events rather than logs, so checking pod events first is essential to identify runtime or scheduling issues before diving into container logs.

Can I extend Kubernetes debugging scripts with additional kubectl tooling?

Yes, the Kubernetes debugging scripts can be extended with additional kubectl tooling and new scripts added under the scripts directory to support broader cluster troubleshooting workflows.