Inspect Kubernetes Pod status, logs, and runtime failures via kubectl.
npx skills add https://github.com/theslashdojo/dojo --skill pods-theslashdojo
Please help me install this Agent Skill. Skill: pods Source: https://github.com/theslashdojo/dojo/tree/main/nodes/kubernetes/pods Command: npx skills add https://github.com/theslashdojo/dojo --skill pods-theslashdojo
Managing and diagnosing individual Kubernetes Pods can be time consuming and error prone when dealing with failing containers, missing logs, scheduling issues, and probe or resource misconfigurations. This Skill centralizes the common Pod operations needed to inspect status, retrieve logs, open interactive shells, port-forward, and interpret events so agents and operators can rapidly identify root causes.
Ask the skill to describe pod my-app in the target namespace and show recent and previous logs for diagnosis.
High-intent search queries and answers about installing and using this skill.
To debug a Kubernetes Pod stuck in CrashLoopBackOff, you need to describe the pod to surface error reasons and exit codes, then retrieve previous container logs to identify the root cause of the runtime failure. This skill automates that diagnostic sequence.
Checking Kubernetes Pod status and events for scheduling failures requires describing the target pod to inspect wide metadata, resource limits, and recent events. This provides the scheduling state and runtime conditions needed to resolve Pending or ImagePullBackOff states.
Yes, you can port-forward to access the pod locally and open an interactive exec shell into the container. This allows you to reproduce issues locally and run real-time diagnostics within the target namespace.
Yes, you need kubectl access to the cluster and namespace to troubleshoot OOMKilled and readiness probe failures. This access enables the required describe, logs, and exec operations to inspect resource limits and probe configurations.
The best way to retrieve previous logs from a restarting Kubernetes container is using the logs operation with the previous flag. This surfaces the crash output from the last terminated instance to help identify why the pod is failing.
kubiyabotExecute kubectl commands to manage Kubernetes clusters.
X-McKayDiagnose Kubernetes pod DNS configuration issues and nameserver limit exceedances.
SnakeODiagnose Kubernetes issues across clusters, pods, services, and RBAC configurations.
eveldDebug Kubernetes workloads using structured locator, analyzer, and pattern-finder workflows.
