skills.rest
ionfury
ionfuryCOMMUNITY
Explore all skills by this author →
GitHub

sre

Diagnose Kubernetes incidents through structured, read-only investigation with 5 Whys.

24|3|Updated Mar 31, 2022
Search Tags:#debugging#troubleshooting#kubernetes#sre#root-cause#incident#5-whys
One-click install
npx skills add https://github.com/ionfury/homelab --skill sre
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sre
Source: https://github.com/ionfury/homelab/tree/main/.claude/skills/sre
Command: npx skills add https://github.com/ionfury/homelab --skill sre

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Diagnose Kubernetes incidents by performing a structured, read-only investigation to identify root causes.

Core Features & Use Cases

  • 5 Whys Analysis: Apply iterative questioning to reach actionable root causes without jumping to conclusions.
  • Phased Investigation: Triage, data collection, correlation, root-cause determination, and remediation guidance.
  • Multi-Source Data: Integrates logs, events, metrics, and configurations to build a cohesive incident picture.
  • Guided Playbook: Provides repeatable steps for common Kubernetes incidents (pod failures, CrashLoopBackOff, networking issues, deployment failures, and Flux/Helm problems).
  • Remediation Guidance: Offers immediate and longer-term mitigation strategies and prevention suggestions.

Quick Start

Run the cluster-health.sh script to capture a read-only health snapshot of the target Kubernetes cluster and namespace.

Frequently Asked Questions about sre

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

FAQPage Schema
How do I diagnose Kubernetes pod failures and find the root cause?▼

Troubleshoot CrashLoopBackOff by collecting multi-source data including pod logs, Kubernetes events, and metrics. Correlate these inputs through a phased investigation to identify the specific deployment or configuration failure causing the continuous restart loop.

Can I use this to investigate Kubernetes networking issues and deployment problems?▼

A 5 Whys analysis works by applying iterative questioning to incident data, forcing you to reach actionable root causes rather than stopping at symptoms. It prevents jumping to conclusions during the root-cause determination phase of Kubernetes incident triage.

Does the Skill support read-only troubleshooting for Flux and Helm problems?▼

Yes, you can capture a read-only health snapshot of your target Kubernetes cluster and namespace by running the cluster-health.sh script. This initiates the triage phase and collects baseline data for diagnosing incidents safely.

What is the best way to troubleshoot a CrashLoopBackOff in Kubernetes?▼

Troubleshoot CrashLoopBackOff by collecting multi-source data including pod logs, Kubernetes events, and metrics. Correlate these inputs through a phased investigation to identify the specific deployment or configuration failure causing the continuous restart loop.

Related Skills

Explore More Software Engineering Skills→
ObolNetworkObolNetwork
10

obol-stack

Monitor Obol Stack Kubernetes pods, logs, services, and deployments via the Kubernetes API.

Official
Intermediate
randybiasrandybias
1

k8s-troubleshooter

Diagnose Kubernetes incidents and collect evidence for triage reports.

Community
Advanced
vmkteamvmkteam
6

investigate

Correlate Sentry, Prometheus, Loki, Kibana, and Nomad data to investigate production incidents.

Official
Advanced
peterfeipeterfei
10

five-whys-skill

Apply the 5 Whys methodology to identify systemic root causes.

Community
Advanced