Pod Troubleshooting

Debug a Kubernetes pod stuck in CrashLoopBackOff by running kubectl describe to inspect events and kubectl logs to check application startup errors. This Skill provides the specific commands to pinpoint whether the failure stems from configuration issues or resource limits.

Diagnose OOMKilled and ImagePullBackOff errors using kubectl status, describe, events, and logs commands. This Skill scopes these kubectl instructions to the openclaw namespace to isolate memory exhaustion and image pull failures.

Troubleshoot Init:Error failures in Kubernetes init containers by executing kubectl logs on the specific container to identify the failing initialization step. This Skill scopes the diagnostic process to pinpoint startup logic errors within the openclaw namespace.

You need kubectl installed to diagnose unhealthy Kubernetes pods because this Skill requires it to interact directly with the Kubernetes API. Kubectl executes the status, describe, and exec commands needed for detailed pod state inspection and remediation.

Your Kubernetes pod is repeatedly restarting due to application startup logic errors, resource limits, or configuration issues. This Skill performs root cause analysis to determine the exact failure trigger, such as OOMKilled or CrashLoopBackOff, within the openclaw namespace.