skills.rest
luiscamaral
luiscamaralCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

troubleshooting-pods

Diagnose failing Kubernetes pods across namespaces with scripted diagnostics.

1|1|Updated Jan 3, 2026
Search Tags:#debugging#kubernetes#diagnostics#kubectl#pod#imagepullbackoff#crashloopbackoff
One-click install
npx skills add https://github.com/luiscamaral/k8s-cell-platform-skills --skill troubleshooting-pods
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshooting-pods
Source: https://github.com/luiscamaral/k8s-cell-platform-skills/tree/main/troubleshooting-pods
Command: npx skills add https://github.com/luiscamaral/k8s-cell-platform-skills --skill troubleshooting-pods

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Diagnoses and debugs pod issues across Kubernetes clusters to quickly identify root causes and restore healthy workloads.

Core Features & Use Cases

  • Quick diagnosis commands to surface failing pods, events, and resource pressure across all namespaces.
  • Diagnostic workflows for common pod problems (CrashLoopBackOff, ImagePullBackOff, OOMKilled, Pending, CreateContainerConfigError) with guided remediation steps.
  • An automated diagnostics script (scripts/collect-diagnostics.sh) that aggregates pod status, logs, events, and node metrics for shareable reports.
  • Reference documentation for common pod errors and layer-specific notes to aid root-cause analysis.

Quick Start

Run diagnostics for a pod by specifying the namespace and pod name.

Frequently Asked Questions about troubleshooting-pods

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

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

Debug a Kubernetes pod stuck in CrashLoopBackOff by running guided diagnostic workflows that aggregate container logs and pod events to identify the root cause. The skill requires kubectl access to the connected cluster to execute its remediation steps.

What is the best way to diagnose ImagePullBackOff errors across namespaces?▼

Diagnose ImagePullBackOff errors across namespaces by running an automated diagnostics script that aggregates failing pod statuses and cluster events. The script collects resource pressure metrics and reference notes to pinpoint image pull failures.

Can I collect Kubernetes pod logs and node metrics for a shareable report?▼

You can collect Kubernetes pod logs and node metrics for a shareable report by executing the automated collect-diagnostics.sh script. It aggregates pod status, events, and node metrics across namespaces into a comprehensive output for root-cause analysis.

Do I need kubectl access to troubleshoot Pending and OOMKilled pods?▼

You need kubectl access to a connected cluster to troubleshoot Pending and OOMKilled pods. The skill uses kubectl access to execute its automated diagnostics scripts and perform comprehensive analysis of the failing workloads.

What common pod errors does this diagnostics workflow support besides CrashLoopBackOff?▼

Besides CrashLoopBackOff, the diagnostics workflow supports common pod errors including ImagePullBackOff, OOMKilled, Pending, and CreateContainerConfigError. It provides layer-specific notes to aid root-cause analysis for these failing workloads.

Related Skills

Explore More Software Engineering Skills→
dieguscldieguscl

k8s-check

Diagnose Kubernetes cluster health by checking pod status, events, resource usage, and restart counts.

Community
Intermediate
openshiftopenshift
71

pod-failure-diagnosis

Classify Kubernetes pod failure modes and output remediation commands.

Official
Intermediate
cnoe-iocnoe-io
392

cluster-resource-health

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

Official
Intermediate
dennisonbertramdennisonbertram
1

k8s-debug

Diagnose Kubernetes pod issues with kubectl workflows and commands.

Community
Advanced