k8s-debug

Diagnose Kubernetes pod and deployment issues using event-first kubectl workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach for diagnosing Kubernetes pod and deployment issues by prioritizing events over logs to speed up root-cause analysis.

Core Features & Use Cases

  • Event-first debugging: check pod events before inspecting logs to identify the root cause of issues like CrashLoopBackOff, ImagePullBackOff, or scheduling failures.
  • Stepwise investigation flow: a repeatable sequence using common kubectl commands (get_pod_events, get_pod_logs, describe_deployment) to quickly verify state and progress.
  • Problem coverage: handles common patterns including CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending Pods, Readiness/Liveness probe failures, evicted pods, and rollout issues.
  • Operational checklist: verify memory/resource limits, recent changes, configuration/secrets, and external service dependencies.

Quick Start

Start debugging a failing pod by listing its events, then fetch logs only if events don’t explain the issue. Move through the recommended steps: get_pod_events → get_pod_logs → describe_deployment.

Frequently Asked Questions about k8s-debug

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

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

To debug a CrashLoopBackOff pod, check pod events first to identify scheduling or configuration failures, then fetch pod logs if events do not reveal the root cause. This event-first approach accelerates diagnosis.

Why does my Kubernetes pod get OOMKilled and how do I diagnose it?

Diagnose an OOMKilled Kubernetes pod by verifying memory and resource limits through pod events and descriptions. Check recent configuration changes and resource constraints to identify why the container exceeded its allocated memory.

What is the best way to troubleshoot Kubernetes ImagePullBackOff errors?

Troubleshoot ImagePullBackOff by inspecting pod events to verify image names and registry credentials. Check configuration and secrets to ensure the deployment manifest has valid authentication details for pulling images.

How do I investigate Kubernetes deployment rollout failures across namespaces?

Investigate Kubernetes deployment rollout failures by describing the deployment to verify its state, then checking pod events and logs. Progress through a stepwise investigation flow to identify readiness or configuration issues.

Can I use kubectl to diagnose Kubernetes pending pods and readiness probe failures?

Yes, you can use kubectl to diagnose pending pods and readiness probe failures. Check pod events to identify scheduling failures or probe configurations, then fetch logs to investigate application-level startup issues.