k8s-debug

Diagnose Kubernetes pod and deployment issues using kubectl and deterministic workflows.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/devkeni/Skills --skill k8s-debug-devkeni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-debug
Source: https://github.com/devkeni/Skills/tree/main/backend-devops/k8s-debug
Command: npx skills add https://github.com/devkeni/Skills --skill k8s-debug-devkeni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Diagnose and fix Kubernetes pod and deployment issues using kubectl.

Core Features & Use Cases

  • Deterministic debugging workflow for Kubernetes clusters
  • Preflight checks, structured diagnostics, and safe remediation guidance
  • Coverage across common Kubernetes pain points: CrashLoopBackOff, Pending, DNS, networking, storage, and rollout issues
  • Supports reproducible workflows with scripts and reference materials for rapid troubleshooting in real clusters

Quick Start

Run the k8s-debug skill from its root directory to initiate a deterministic Kubernetes diagnosis workflow.

Frequently Asked Questions about k8s-debug

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

FAQPage Schema
How do I troubleshoot Kubernetes pods stuck in CrashLoopBackOff?

Troubleshoot Kubernetes CrashLoopBackOff errors using deterministic workflows with kubectl. Apply preflight checks and structured diagnostic scripts to identify pod failures and execute guided remediation steps for rapid cluster recovery.

What is the best way to debug Kubernetes DNS and networking problems?

Debug Kubernetes DNS and networking problems through structured kubectl diagnostics and reference workflows. Execute safety-first preflight checks to isolate network debugging issues and apply deterministic remediation guidance across clusters.

How do I resolve Kubernetes deployment rollout obstacles?

Resolve Kubernetes deployment rollout obstacles by running deterministic diagnostic workflows with kubectl. Identify blocking conditions through pod diagnostics and apply structured remediation steps to restore cluster health.

Does this Kubernetes debugging approach require specific cluster configurations?

This Kubernetes debugging approach requires kubectl access and applies across clusters without specific configuration dependencies. It uses preflight checks and reference scripts to ensure safety-first, reproducible troubleshooting regardless of cluster state.

Why are my Kubernetes pods stuck in Pending state and how can I fix them?

Kubernetes pods stuck in Pending state often face storage binding or resource constraints. Diagnose these pod failures using deterministic kubectl workflows and structured diagnostics to pinpoint issues and apply guided remediation steps.

Can I use kubectl to safely diagnose storage binding issues in Kubernetes?

Yes, safely diagnose storage binding issues in Kubernetes using kubectl with deterministic workflows. The safety-first approach applies preflight checks and structured diagnostics to identify binding obstacles and guide remediation without risking cluster stability.