skills.rest
erwinv2k-TKG
erwinv2k-TKGCOMMUNITY
Explore all skills by this author →
GitHub

infrastructure

Diagnose Kubernetes pod failures and AWS cloud infrastructure issues using debugging scripts.

Updated Mar 26, 2026
Search Tags:#debugging#aws#kubernetes#cloud infrastructure#sre#incident investigation#pod crashes
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill infrastructure-erwinv2k-tkg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: infrastructure
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/incidentfox/sre-agent/.claude/skills/infrastructure
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill infrastructure-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investigating pod crashes, stuck deployments, and cloud resource failures requires running many kubectl and AWS commands manually. This Skill routes infrastructure incidents to the right debugging domain and provides ready-to-run diagnostic scripts. ## Core Features & Use Cases - Kubernetes Debugging: Diagnose CrashLoopBackOff, OOMKilled, Pending pods, and stuck deployments using scripts for events, logs, resources, and rollout history. - AWS Troubleshooting: Investigate EC2, ECS, Lambda, and CloudWatch issues through the dedicated AWS domain. - Use Case: A pod in the otel-demo namespace keeps restarting. Run the get_events.py script first to inspect pod events, then pull logs with get_logs.py to identify the root cause. ## Quick Start Ask the agent to investigate why a pod is in CrashLoopBackOff in the otel-demo namespace using the infrastructure debugging scripts.

Frequently Asked Questions about infrastructure

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

FAQPage Schema
How do I debug a pod in CrashLoopBackOff in Kubernetes?▼

Check pod events first using the get_events.py script with the pod name and namespace, since events reveal the immediate failure cause. Then retrieve container logs with get_logs.py using the --tail flag to inspect recent output before the crash.

How to investigate an OOMKilled pod in Kubernetes?▼

An OOMKilled pod exceeded its memory limits, so check resource configuration with the get_resources.py script. Compare the container's memory requests and limits against actual usage to decide whether to raise limits or fix a memory leak.

What should I check when a Kubernetes deployment is stuck?▼

Check the rollout history using the get_history.py script to see which revision is failing. Combine this with pod events from get_events.py to identify image pull errors, failed probes, or resource constraints blocking the rollout.

Does this skill support AWS infrastructure debugging?▼

Yes, it includes an AWS domain covering EC2, ECS, Lambda, and CloudWatch issues through the infrastructure-aws sub-skill. Kubernetes and AWS are handled as separate domains routed from the main infrastructure entry point.

Why is my Kubernetes pod stuck in Pending state?▼

Pending pods usually indicate scheduling failures from insufficient node resources, unbound volumes, or taint mismatches. Run get_events.py to see scheduler messages, then check node capacity and resource requests to find the blocker.

Related Skills

Explore More Software Engineering Skills→
dmzoneilldmzoneill
2

debug-prod

Diagnose production issues by analyzing Kubernetes pods, logs, metrics, alerts, and deployments.

Community
Advanced
patricio0312revpatricio0312rev
5

incident-runbook-generator

Generate incident runbooks with steps, owners, rollback procedures, and communication templates.

Community
Advanced
imMamdouhaboammarimMamdouhaboammar

datadog-cli

Query Datadog logs, metrics, and dashboards via command-line interface.

Community
Advanced
nebinfranebinfra

neb-cluster-health

Identify and report health and sync issues across ArgoCD-managed Kubernetes clusters.

Official
Advanced