skills.rest
david-driscoll
david-driscollCOMMUNITY
Explore all skills by this author →
Website𝕏@david_dotnetGitHub

sre

Diagnose Kubernetes incidents via triage, evidence collection, and 5 Whys root cause analysis.

1|Updated Apr 6, 2025
Search Tags:#root cause analysis#kubernetes#network policy#incident investigation#5 whys#cilium hubble#flux helmrelease
One-click install
npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill sre-david-driscoll
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sre
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/sre
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill sre-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you debug Kubernetes incidents by turning confusing symptoms like stuck pods or failing workloads into a disciplined root-cause analysis you can act on.

Core Features & Use Cases

  • 5 Whys root cause analysis: drives investigations past surface errors to identify the underlying failure mechanism.
  • Incident triage and evidence gathering: guides rapid collection of pod state, events timeline, logs (including previous container instances), and resource signals.
  • Network policy debugging with Cilium/Hubble: explains how to validate namespace labels and observe DROPPED traffic to pinpoint blocked paths.
  • Operational recovery patterns: includes safe guidance for stalled HelmReleases (suspend/resume) and Flux promotion pipeline troubleshooting.

Quick Start

Use the sre skill to investigate a CrashLoopBackOff pod in the database namespace and determine the most likely root cause using logs, events, and 5 Whys.

Frequently Asked Questions about sre

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

FAQPage Schema
How do I diagnose a Kubernetes CrashLoopBackOff to find the root cause?▼

Diagnose a CrashLoopBackOff by triaging pod state, collecting previous container logs and events, and applying 5 Whys analysis to identify the underlying failure mechanism driving the pod lifecycle crash.

Why are my Kubernetes pods stuck in Pending or OOMKilled states?▼

Kubernetes pods stuck in Pending or OOMKilled states require incident triage that correlates resource signals, pod events, and logs to pinpoint the failure mechanism and guide root cause remediation.

How do I debug Cilium network policy drops using Hubble?▼

Debug Cilium network policy drops by validating namespace labels and using Hubble observation to detect DROPPED traffic, pinpointing the blocked network paths causing degraded services.

What is the best way to troubleshoot a stalled Flux HelmRelease?▼

Troubleshoot a stalled Flux HelmRelease by following operational recovery patterns that safely suspend and resume the deployment pipeline, allowing you to bypass degraded states and investigate the failure.

When should I use 5 Whys analysis for Kubernetes incident investigation?▼

Use 5 Whys analysis for Kubernetes incident investigation when you need to drive past surface errors like ImagePullBackOff and determine the underlying root cause mechanism through multi-source evidence correlation.

Related Skills

Explore More Software Engineering Skills→
filipemottafilipemotta
1

k8s-troubleshooter

Diagnose and resolve Kubernetes issues across clusters and workloads.

Community
Advanced
patricio0312revpatricio0312rev
5

flaky-test-detective

Diagnose flaky tests by identifying root causes like timing and shared state.

Community
Advanced
AI-Foundry-CoreAI-Foundry-Core
4

service-mesh-observability

Configure tracing, metrics, dashboards, and SLOs for service mesh deployments.

Official
Advanced
Shakudo-ioShakudo-io

k8s-troubleshooter

Diagnose and remediate Kubernetes incidents and performance issues in production clusters.

Official
Advanced