Does this skill provide specific kubectl commands?

Yes, it includes a wide range of optimized commands for describing resources, viewing previous logs, monitoring events, and checking resource usage via metrics-server.

What common Kubernetes errors does this skill help solve?

The skill provides specific diagnostic steps and solutions for CrashLoopBackOff, ImagePullBackOff, OOMKilled, Pending pods, Service connectivity issues, PVC binding failures, and RBAC errors.

Does it support modern Kubernetes debugging features?

Yes, it provides specific guidance on using ephemeral containers with the 'kubectl debug' command, which is the modern standard for debugging pods and nodes.

Can I use this for troubleshooting network and service issues?

Absolutely. It includes debugging steps for service selectors, endpoint verification, NetworkPolicies, and testing connectivity from within the cluster using debug pods.

How does the four-phase debugging methodology work?

It guides you through a logical sequence: 1) Gathering Information, 2) Checking Logs and Metrics, 3) Interactive Investigation (exec/debug), and 4) Validation and Fix application.

Kubernetes Troubleshooting & Debugging

Name: Kubernetes Troubleshooting & Debugging
Author: SnakeO

bySnakeO

Deployment & DevOps

Systematically diagnoses and resolves Kubernetes cluster issues including pod failures, connectivity problems, and resource constraints using a structured four-phase methodology.

About

This skill provides a comprehensive framework for identifying and fixing root causes of common Kubernetes errors such as CrashLoopBackOff, OOMKilled, and ImagePullBackOff. By implementing a structured four-phase debugging methodology—gathering info, checking logs/metrics, interactive investigation, and validation—it empowers developers and DevOps engineers to navigate complex cluster environments. It includes an extensive library of optimized kubectl commands, ephemeral debug container workflows, and specific troubleshooting paths for RBAC, PVC binding, and service discovery failures.

Key Features

Four-phase systematic debugging methodology for consistent results
Interactive investigation guides using ephemeral debug containers and netshoot
0 GitHub stars
Deep-dive kubectl command reference for pods, nodes, services, and events
Comprehensive error pattern recognition for CrashLoopBackOff, OOMKilled, and more
Specialized workflows for RBAC permissions and Persistent Volume troubleshooting

Use Cases

Investigating resource scheduling failures and persistent volume binding errors
Troubleshooting complex network connectivity and service discovery issues between microservices
Resolving container crash loops and startup failures in production or staging environments

About

Key Features

Four-phase systematic debugging methodology for consistent results
Interactive investigation guides using ephemeral debug containers and netshoot
0 GitHub stars
Deep-dive kubectl command reference for pods, nodes, services, and events
Comprehensive error pattern recognition for CrashLoopBackOff, OOMKilled, and more
Specialized workflows for RBAC permissions and Persistent Volume troubleshooting

Use Cases

Investigating resource scheduling failures and persistent volume binding errors
Troubleshooting complex network connectivity and service discovery issues between microservices
Resolving container crash loops and startup failures in production or staging environments