skills.rest
vib795
vib795COMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug-eks

...

Updated Apr 16, 2026
Search Tags:#debugging#troubleshooting#kubernetes#eks#kubectl#triage#pod
One-click install
npx skills add https://github.com/vib795/copilot-anatomy --skill debug-eks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-eks
Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/debug-eks
Command: npx skills add https://github.com/vib795/copilot-anatomy --skill debug-eks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pod troubleshooting for Kubernetes/EKS when pods fail to start, crash, or behave unexpectedly, including common failure modes like OOMKilled, ImagePullBackOff, and CrashLoopBackOff.

Core Features & Use Cases

  • Deterministic triage sequence to identify pod health, events, and logs.
  • Kubernetes/EKS-focused guidance applicable to both dev and prod clusters.
  • Real-world scenarios: diagnosing pod startup failures, crashes, and intermittent issues in a live cluster.

Quick Start

Follow the triage order to rapidly diagnose a failing pod in your Kubernetes cluster.

Frequently Asked Questions about debug-eks

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

FAQPage Schema
What are the most common Kubernetes pod failure modes to check for?▼

Common Kubernetes pod failure modes include OOMKilled, ImagePullBackOff, and CrashLoopBackOff. Triage these failures by reading pod events and logs to identify the root cause of startup crashes or unexpected behavior in your EKS cluster.

How do I diagnose a CrashLoopBackOff or OOMKilled pod using kubectl?▼

Diagnose CrashLoopBackOff or OOMKilled pods by using kubectl to check pod health and read events. This deterministic triage sequence pinpoints resource limits or application errors causing the pod to crash or fail to start in your EKS environment.

Can this triage sequence be used for both development and production EKS clusters?▼

Yes, this triage sequence is applicable for diagnosing pod startup failures and crashes in both development and production EKS clusters. It provides Kubernetes-focused guidance to rapidly identify intermittent issues and root causes.

Why are my Kubernetes pods failing to start with an ImagePullBackOff error?▼

Kubernetes pods fail with ImagePullBackOff when they cannot retrieve the specified container image. Identify this by reading pod events during triage to verify image names, tags, and registry access permissions in your EKS cluster.

What is the best way to troubleshoot intermittent pod issues in a live EKS cluster?▼

The best way to troubleshoot intermittent pod issues in a live EKS cluster is following a deterministic triage order. Read pod events and logs systematically to diagnose unexpected behavior and determine root causes rapidly.

Related Skills

Explore More Software Engineering Skills→
huynguyenhhuynguyenh
3

hnh-k8s

Run kubectl commands to debug and monitor Kubernetes EKS clusters.

Community
Intermediate
arbazkhan971arbazkhan971
26

k8s

Manage Kubernetes deployments and validate Helm charts and manifests.

Community
Advanced
cnoe-iocnoe-io
392

cluster-resource-health

Query EKS clusters via kubectl and report pod, node, and resource health.

Official
Intermediate
openshiftopenshift
71

pod-failure-diagnosis

Classify Kubernetes pod failure modes and output remediation commands.

Official
Intermediate