skills.rest
dennisonbertram
dennisonbertramCOMMUNITY
Explore all skills by this author →
Website𝕏@DennisonBertramGitHub

k8s-debug

Diagnose Kubernetes pod issues with kubectl workflows and commands.

1|1|Updated Mar 6, 2026
Search Tags:#debugging#networking#kubernetes#kubectl#crashloopbackoff#pod-diagnostics#oomKilled
One-click install
npx skills add https://github.com/dennisonbertram/go-agent-harness --skill k8s-debug-dennisonbertram
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-debug
Source: https://github.com/dennisonbertram/go-agent-harness/tree/main/skills/k8s-debug
Command: npx skills add https://github.com/dennisonbertram/go-agent-harness --skill k8s-debug-dennisonbertram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kubernetes pod debugging and troubleshooting for common Kubernetes pod issues including CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, and networking problems, enabling rapid isolation and remediation.

Core Features & Use Cases

  • Deterministic workflows: step-by-step commands to inspect pods, events, logs, and resources.
  • Broad applicability: handles single-pod issues and multi-pod incidents across namespaces in development, staging, and production environments.
  • Use Case: Imagine a failing pod in namespace prod that cycles CrashLoopBackOff; this skill guides you through quick diagnostics and remediation steps.

Quick Start

Run the kubectl-based workflow to diagnose a problematic pod by replacing placeholders with your pod name and namespace.

Frequently Asked Questions about k8s-debug

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

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

To debug a Kubernetes pod stuck in CrashLoopBackOff, you gather pod status, describe events, and inspect logs using kubectl. This workflow isolates the failure cause and provides clear remediation commands with safeguards.

What is the best way to troubleshoot OOMKilled pods in Kubernetes?▼

Troubleshooting OOMKilled pods involves inspecting resource usage and pod events to identify memory limits. The workflow guides you through kubectl commands to check resource requests and limits for rapid remediation.

Can I diagnose Kubernetes networking issues across multiple namespaces?▼

Yes, you can diagnose Kubernetes networking issues across multiple namespaces. The workflow handles single-pod issues and multi-pod incidents in development, staging, and production environments using kubectl.

How do I find out why my Kubernetes pod is in a Pending state?▼

To find out why a Kubernetes pod is in a Pending state, you describe events and inspect resource usage via kubectl. This helps identify scheduling failures or resource constraints preventing deployment.

Does this kubectl troubleshooting workflow work for staging and production environments?▼

Yes, this kubectl troubleshooting workflow works for staging and production environments. It applies deterministic workflows to gather pod status and logs for incidents across various namespaces.

Related Skills

Explore More Software Engineering Skills→
paulanunes85paulanunes85
1

kubectl-cli

Execute kubectl commands to diagnose and fix Kubernetes cluster issues in AKS and ARO environments.

Community
Intermediate
abatiloabatilo
10

kubernetes

Automate Kubernetes cluster management with kubectl, Helm, and Kustomize.

Community
Advanced
cnoe-iocnoe-io
392

cluster-resource-health

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

Official
Intermediate
microsoftmicrosoft
242

azure-observability

Automate Azure observability workflows for monitoring and diagnosing cloud workloads.

Official
Advanced