// Infrastructure debugging for Kubernetes and AWS. Use when investigating pod crashes, deployment issues, resource problems, container failures, or cloud infrastructure issues.
| name | infrastructure |
| description | Infrastructure debugging for Kubernetes and AWS. Use when investigating pod crashes, deployment issues, resource problems, container failures, or cloud infrastructure issues. |
For pod crashes, deployment issues, resource problems, container failures.
Use: /infrastructure-kubernetes
For EC2, ECS, Lambda, and CloudWatch issues.
Use: /infrastructure-aws
# List pods in namespace
python .claude/skills/infrastructure-kubernetes/scripts/list_pods.py -n otel-demo
# Get pod events (ALWAYS check first!)
python .claude/skills/infrastructure-kubernetes/scripts/get_events.py <pod-name> -n otel-demo
# Get pod logs
python .claude/skills/infrastructure-kubernetes/scripts/get_logs.py <pod-name> -n otel-demo --tail 100
| Symptom | First Action | Script |
|---|---|---|
| Pod CrashLoopBackOff | Check events | get_events.py |
| Pod OOMKilled | Check resources | get_resources.py |
| Pod Pending | Check events + nodes | get_events.py |
| Deployment stuck | Check rollout history | get_history.py |
Kubernetes debugging methodology and scripts. Use for pod crashes, CrashLoopBackOff, OOMKilled, deployment issues, resource problems, or container failures.
GitLab project management, CI/CD pipelines, merge requests, and code review. Use when investigating GitLab projects, pipeline failures, merge requests, commits, or issues.
Slack integration for incident communication. Use when searching for context in incident channels, posting status updates, or finding discussions about issues.
ClickUp project management integration for incident tracking and task management
AWS cloud infrastructure inspection. Use when investigating EC2 instances, ECS tasks/services, Lambda functions, CloudWatch logs/metrics, or AWS resource issues.
Safe remediation actions for Kubernetes. Use when proposing or executing pod restarts, deployment scaling, or rollbacks. Always use dry-run first.