skills.rest
Canepro
CaneproCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

k8s-sre-triage

Classify Kubernetes runtime incidents using evidence from cluster snapshot scripts.

Updated Mar 18, 2026
Search Tags:#kubernetes#evidence#gitops#triage#sre#incident
One-click install
npx skills add https://github.com/Canepro/codex-skills --skill k8s-sre-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-sre-triage
Source: https://github.com/Canepro/codex-skills/tree/main/skills/k8s-sre-triage
Command: npx skills add https://github.com/Canepro/codex-skills --skill k8s-sre-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Investigates Kubernetes and container runtime incidents using an evidence-first triage approach to minimize blast radius and accelerate recovery.

Core Features & Use Cases

  • Establish scope and collect baseline cluster state using the provided scripts.
  • Classify the incident into common failure modes (scheduling, runtime, networking, storage, GitOps, provider issues) with evidence.
  • Recommend GitOps-safe remediation steps and verification plan to restore services and prevent drift.
  • Use cases include pods in CrashLoopBackOff, stuck rollouts, networking or DNS issues, storage failures, and GitOps sync blockers.

Quick Start

Describe the incident, capture the current cluster context, and follow the evidence-first triage workflow to determine the safest remediation path.

Frequently Asked Questions about k8s-sre-triage

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

FAQPage Schema
How do I triage Kubernetes CrashLoopBackOff incidents using an evidence-first approach?▼

To triage Kubernetes CrashLoopBackOff incidents, classify the failure mode and use read-only kubectl access with scripts like k8s_snapshot.sh to collect baseline cluster state as evidence before remediating.

What is the best way to investigate stuck Kubernetes rollouts and GitOps sync blockers?▼

The best way to investigate stuck Kubernetes rollouts and GitOps blockers is to apply an evidence-first triage workflow that captures cluster context and classifies scheduling or GitOps issues to recommend safe remediation steps.

Do I need read-only cluster context to troubleshoot Kubernetes networking and storage failures?▼

Yes, you need read-only cluster context and kubectl access to safely troubleshoot Kubernetes networking and storage failures, utilizing provided scripts to gather evidence without risking further cluster drift.

How does an evidence-first SRE triage workflow minimize blast radius during a Kubernetes incident?▼

An evidence-first SRE triage workflow minimizes blast radius by establishing incident scope and collecting baseline cluster state before action, ensuring Kubernetes runtime remediation is guided by verified evidence.

Can I use kubectl scripts to classify Kubernetes runtime incidents and prevent configuration drift?▼

You can use provided kubectl scripts like pod_triage.sh to collect evidence and classify Kubernetes runtime incidents, which then recommends GitOps-safe remediation steps to restore services and prevent drift.

Related Skills

Explore More Software Engineering Skills→
initializinitializ
186

k8s-incident-triage

Triage Kubernetes workloads, pods, and namespaces using kubectl commands.

Official
Advanced
jeremylongshorejeremylongshore
2.6k

detecting-infrastructure-drift

Detect infrastructure drift between current state and desired configuration.

Community
Advanced
iulianditaiuliandita
2

cluster-health

Run read-only Kubernetes cluster health checks and generate status reports.

Community
Advanced
xiaoshenmingxiaoshenming

monitor-ci

Monitor Nx Cloud CI pipelines and trigger self-healing fixes via a subagent.

Community
Advanced