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>