k8s-incident

Run Kubernetes incident diagnostics and generate runbooks with Python scripts.

944|179|Updated Mar 23, 2025
One-click install
npx skills add https://github.com/rohitg00/kubectl-mcp-server --skill k8s-incident
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-incident
Source: https://github.com/rohitg00/kubectl-mcp-server/tree/main/kubernetes-skills/claude/k8s-incident
Command: npx skills add https://github.com/rohitg00/kubectl-mcp-server --skill k8s-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Kubernetes incidents often hinder operations due to manual triage, inconsistent runbooks, and scattered diagnostics. This skill provides ready-to-use runbooks and a structured diagnostic workflow to accelerate root cause analysis and remediation.

Core Features & Use Cases

  • Runbooks and checklists for Pod Failures, Node Issues, Network Problems, and Emergency Actions.
  • A Python-based diagnostics script that collects cluster health, resources, events, pod logs, and networking/storage state on demand.
  • Automated incident reporting with triage summaries and a human-readable incident report.

Quick Start

Invoke the k8s-incident skill during an active incident to generate runbooks and diagnostics. Example: Run k8s-incident with context 'prod' and namespace 'default' to triage a failing pod and produce a diagnostic report.

Frequently Asked Questions about k8s-incident

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

FAQPage Schema
How do I triage Kubernetes pod failures and node issues during an active outage?

To triage Kubernetes pod failures and node issues during an outage, this skill provides targeted runbooks and a Python diagnostics script that collects cluster health, events, and pod logs to generate a human-readable incident report.

What is the best way to automate Kubernetes incident response diagnostics across multiple clusters?

Automating Kubernetes incident response diagnostics across multi-cluster environments is handled by a Python script that runs modular checks on nodes, system pods, services, endpoints, and network policies, outputting both machine-parseable payloads and human-readable reports.

Can I collect Kubernetes network policy and PVC state for incident troubleshooting?

Yes, you can collect Kubernetes network policy and PVC state for incident troubleshooting, as the diagnostics script specifically includes modular checks for network_policies, PVCs, services, and endpoints alongside cluster events and logs.

How do I generate a structured incident report from Kubernetes cluster events and pod logs?

Generating a structured incident report from Kubernetes cluster events and pod logs is accomplished by running the diagnostics script, which aggregates resources and events into a triage summary with both machine-parseable diagnostics and a human-readable format.

Does this Kubernetes diagnostics tool require any external dependencies or plugins?

No external dependencies or plugins are required for this Kubernetes diagnostics tool, as the skill operates independently using its internal Python scripts to gather cluster state and execute incident response runbooks.

Why use runbooks for Kubernetes emergency actions instead of manual kubectl commands?

Using runbooks for Kubernetes emergency actions ensures consistent remediation and eliminates scattered manual kubectl commands, accelerating root cause analysis by structuring diagnostics for outages, network problems, and node failures into a repeatable workflow.