k8s-debug

Diagnose Kubernetes cluster failures using kubectl inspection and log analysis.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/villadalmine/infra --skill k8s-debug-villadalmine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-debug
Source: https://github.com/villadalmine/infra/tree/main/.agents/skills/k8s-debug
Command: npx skills add https://github.com/villadalmine/infra --skill k8s-debug-villadalmine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubectl, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you diagnose Kubernetes failures systematically, so you can quickly isolate why pods, services, nodes, volumes, or observability components are not behaving as expected.

Core Features & Use Cases

  • Pod and workload triage: Check status, events, restart loops, image pulls, and resource limits when a workload fails to start.
  • Service and networking checks: Verify endpoints, selectors, port alignment, and network policies when traffic cannot reach a service.
  • Cluster health and storage debugging: Inspect node pressure, top resource consumers, persistent volume binding, and common control-plane or add-on failures.
  • Real-world example: A Grafana dashboard stops loading because Loki is unreachable; this Skill guides you through pod status, datasource config, service connectivity, and logs until the root cause is found.

Quick Start

Use this skill to inspect the failing namespace, review recent events, and collect pod, node, and log evidence before making any Kubernetes changes.

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 or failing to start?

To troubleshoot Kubernetes pod startup failures, inspect pod status, review recent cluster events, and analyze container logs to isolate restart loops, image pull errors, or resource limit constraints.

Why is my Kubernetes service unreachable and how do I debug network connectivity?

Debug Kubernetes service connectivity by verifying endpoint readiness, validating selector label matches, checking port alignment, and reviewing network policies to ensure traffic routes correctly to target pods.

How do I diagnose node pressure and persistent volume binding issues in a multi-node cluster?

Diagnose Kubernetes node pressure and persistent volume issues by inspecting node resource consumption, checking top resource consumers, and verifying persistent volume claims and binding states across the cluster.

Does this debugging approach work for observability stacks like Loki, Tempo, and ArgoCD?

Yes, this debugging approach applies to observability stack failures, guiding targeted kubectl-based inspection and log analysis to resolve probe and connectivity issues for Loki, Tempo, Alloy, and ArgoCD.

Can I use kubectl to debug ARM64 nodes in a multi-node Kubernetes cluster?

Yes, you can use kubectl-based inspection to debug ARM64 architectures in multi-node Kubernetes clusters, systematically reviewing node health, workload statuses, and control-plane add-on failures.

What is the best way to find the root cause when a Grafana dashboard stops loading because Loki is unreachable?

The best way to debug unreachable Loki is to systematically check pod status, verify datasource configuration, validate service connectivity, and analyze logs until the root cause is found.