Diagnoses Kubernetes pod crash failures by analyzing statuses, events, and previous logs.
npx skills add https://github.com/scitix/siclaw --skill pod-crash-debug
Please help me install this Agent Skill. Skill: pod-crash-debug Source: https://github.com/scitix/siclaw/tree/main/skills/core/pod-crash-debug Command: npx skills add https://github.com/scitix/siclaw --skill pod-crash-debug
This Skill helps SREs and DevOps engineers quickly diagnose and identify the root cause of common pod failures in Kubernetes, such as CrashLoopBackOff, OOMKilled, Error, and RunContainerError.
Use the pod-crash-debug skill to diagnose the pod named 'my-app-pod' in the 'production' namespace.
High-intent search queries and answers about installing and using this skill.
To diagnose a Kubernetes pod in CrashLoopBackOff, this Skill analyzes pod status, events, and previous container logs to pinpoint root causes like application exceptions or configuration issues. It systematically checks exit codes against known failure patterns.
OOMKilled errors in Kubernetes pods occur when containers exceed their memory limits. This Skill identifies out-of-memory errors by analyzing pod status and events, matching observed resource constraints against known Kubernetes failure patterns.
To find the root cause of a RunContainerError in Kubernetes, this Skill analyzes pod events and previous container logs to identify configuration issues or application exceptions. It requires kubectl to interact with the Kubernetes API for failure analysis.
Yes, you need kubectl installed and configured to debug pod crashes in a production namespace. This Skill requires kubectl to interact with the Kubernetes API, retrieve pod events, and fetch previous container logs for root cause identification.
The best way to troubleshoot Kubernetes pods that keep restarting is to analyze pod status, events, and previous container logs. This Skill systematically matches observed errors and exit codes against known patterns to provide actionable analysis.
A Kubernetes pod fails with an Error status immediately after starting due to application exceptions or configuration issues. This Skill diagnoses the failure by analyzing previous container logs and pod events to identify the specific root cause.
keiretsu-labsDiagnose Kubernetes pod failures with kubectl commands in the openclaw namespace.
willform-aiDiagnose Kubernetes deployment issues on Willform Agent from pod status and logs.
cnoe-ioQuery EKS clusters via kubectl and report pod, node, and resource health.
dennisonbertramDiagnose Kubernetes pod issues with kubectl workflows and commands.
