troubleshooting

Name: troubleshooting
Availability: InStock
Author: ryukyagamilight

Diagnose Kubernetes cluster issues with kubectl commands and log analysis.

1|Updated Jan 31, 2026

Search Tags:#troubleshooting #networking #debug #kubernetes #diagnosis #k8s #cluster

Ready to run

npx skills add https://github.com/ryukyagamilight/terminal-skills --skill troubleshooting-ryukyagamilight

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/ryukyagamilight/terminal-skills/tree/main/kubernetes/troubleshooting
Command: npx skills add https://github.com/ryukyagamilight/terminal-skills --skill troubleshooting-ryukyagamilight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users diagnose and resolve issues within Kubernetes clusters by providing commands and guidance for troubleshooting various components and scenarios.

Core Features & Use Cases

Cluster State Analysis: Check the health and status of nodes, pods, and system components.
Pod Troubleshooting: Diagnose common pod issues like Pending, ImagePullBackOff, CrashLoopBackOff, and OOMKilled.
Network Diagnostics: Troubleshoot service connectivity, DNS resolution, and network policies.
Storage Issues: Identify problems with Persistent Volumes (PVs) and Persistent Volume Claims (PVCs).
Resource Management: Analyze resource quotas and usage.
Log Analysis: Collect and review container and system logs.
Debugging Tools: Utilize kubectl debug and temporary pods for in-depth analysis.
Use Case: When a critical application in your Kubernetes cluster becomes unresponsive, you can use this Skill to systematically check pod status, review logs, examine network configurations, and identify the root cause of the failure.

Quick Start

Use the troubleshooting skill to check the status of all nodes in the Kubernetes cluster.

Frequently Asked Questions about troubleshooting

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

FAQPage Schema

How do I troubleshoot Kubernetes pods stuck in CrashLoopBackOff or Pending states?▼

To troubleshoot Kubernetes pods in CrashLoopBackOff or Pending states, you need to check pod status, review container logs, and inspect resource allocation. This diagnostic process identifies whether failures stem from application crashes, insufficient resources, or missing dependencies.

What is the best way to diagnose Kubernetes cluster network connectivity and DNS resolution issues?▼

Diagnosing Kubernetes network connectivity and DNS issues involves checking service configurations, testing DNS resolution, and verifying network policies. This approach isolates whether connectivity failures originate from misconfigured services or blocked traffic between pods.

How do I use kubectl debug to analyze unresponsive applications in a production cluster?▼

You can use `kubectl debug` to inject temporary pods into your production cluster for in-depth analysis of unresponsive applications. This mechanism allows you to inspect the environment and run diagnostics without altering the original workload.

Why are my Kubernetes Persistent Volume Claims stuck in a Pending state?▼

Kubernetes Persistent Volume Claims remain Pending when storage provisioning fails or no matching Persistent Volumes exist. Troubleshooting storage issues requires examining PVC events and verifying that the requested storage class and capacity are available.

Can I analyze resource quotas and system component logs to find the root cause of node failures?▼

Yes, you can analyze resource quotas and collect system logs to find root causes of Kubernetes node failures. Reviewing node health metrics alongside resource allocation reveals whether nodes are overwhelmed by CPU or memory constraints.