skills.rest
rohitg00
rohitg00COMMUNITY
Explore all skills by this author →
𝕏@ghumare64GitHub

k8s-troubleshoot

Diagnose Kubernetes pod and node issues using kubectl-mcp-server tools and embedded scripts.

944|179|Updated Mar 23, 2025
Search Tags:#troubleshooting#logs#kubernetes#diagnostics#kubectl#pods
One-click install
npx skills add https://github.com/rohitg00/kubectl-mcp-server --skill k8s-troubleshoot-rohitg00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-troubleshoot
Source: https://github.com/rohitg00/kubectl-mcp-server/tree/main/kubernetes-skills/claude/k8s-troubleshoot
Command: npx skills add https://github.com/rohitg00/kubectl-mcp-server --skill k8s-troubleshoot-rohitg00

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables fast debugging and diagnostics for Kubernetes clusters, focusing on pods, nodes, and workloads to shorten mean time to recovery.

Core Features & Use Cases

  • Comprehensive pod diagnostics: status, description, logs, events, and metrics to triage issues quickly.
  • Guided troubleshooting workflows: step-by-step sequences for common issues like CrashLoopBackOff, ImagePullBackOff, and Pending pod states.
  • Multi-context and multi-namespace support: operate across clusters and namespaces with context-aware tooling.
  • Use Case: When a pod enters CrashLoopBackOff, run diagnostics to identify root causes and apply fixes efficiently.

Quick Start

Use the k8s-troubleshoot skill to diagnose a pod named my-app-1 in namespace default.

Frequently Asked Questions about k8s-troubleshoot

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

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

To troubleshoot a Kubernetes pod in CrashLoopBackOff, collect its status, description, and logs to identify the crash root cause. This guided workflow collects events and metrics to triage the issue and accelerate recovery.

What is the best way to diagnose Kubernetes nodes reporting NotReady?▼

The best way to diagnose Kubernetes nodes reporting NotReady is to collect node descriptions and events. Analyzing these metrics isolates the workload or network problem causing the node failure in your staging or production cluster.

How do I get Kubernetes pod logs across multiple namespaces?▼

Get Kubernetes pod logs across multiple namespaces using multi-context aware tooling. This collects descriptions, events, and logs across different clusters and namespaces to triage workload issues quickly.

Can I use kubectl to diagnose Pending pod states in production clusters?▼

Yes, you can use kubectl to diagnose Pending pod states in production clusters. Guided workflows collect pod metrics and events to identify why workloads remain pending and help apply targeted fixes.

Why does my Kubernetes workload experience ImagePullBackOff and how do I fix it?▼

Your Kubernetes workload experiences ImagePullBackOff due to image retrieval failures. Guided workflows collect pod descriptions and events to identify the retrieval error and apply the correct configuration fix.

Related Skills

Explore More Software Engineering Skills→
ryukyagamilightryukyagamilight
1

troubleshooting

Diagnose Kubernetes cluster issues with kubectl commands and log analysis.

Community
Advanced
jMertajMerta
130

ci-fix

Diagnose and patch failing GitHub Actions CI workflows using the GitHub CLI.

Community
Intermediate
htafollahtafolla
5

log-monitor

Analyze log streams, detect patterns, and trigger threshold-based alerts.

Community
Intermediate
scitixscitix
225

volcano-diagnose-pod

Diagnose Volcano-managed Pod scheduling failures via kubectl cluster state queries.

Official
Intermediate