k8s-debug

Debugging a Kubernetes pod in CrashLoopBackOff requires retrieving previous container logs and analyzing recent pod events. This skill enforces a structured workflow to isolate the root cause by inspecting runtime errors and environment configurations safely without applying destructive changes.

Troubleshooting ImagePullBackOff errors in kubectl involves checking pod status and events to identify image name or registry credential issues. This skill guides you through evaluating kubectl event outputs to pinpoint the exact failure and propose safe remediation steps.

Finding out why a Kubernetes deployment is not ready requires analyzing pod status, events, and readiness probes. This skill walks you through a structured debugging workflow to identify readiness problems, inspect container environments, and validate service access via port-forwarding.

Yes, you can use this workflow to debug pods across CI pipelines and development environments. The skill applies to live clusters and various contexts by enforcing cluster context awareness and safe kubectl usage to triage issues like OOMKilled without risking destructive changes.

Yes, this Kubernetes debugging process supports using exec to enter containers, inspect environments, and validate networking. It also includes resource monitoring and port-forward capabilities to validate service access and performance while maintaining safe debugging steps.