| name | pod-failure-triage |
| description | Triage Kubernetes pods in CrashLoopBackOff, ImagePullBackOff, Pending, OOMKilled, or probe failure states. |
Pod Failure Triage
Use this skill when investigating unhealthy pods or workload rollouts.
Workflow
- List pods in the target namespace with
k8s_get_resources.
- Describe the affected pod with
k8s_describe_resource.
- Read pod logs with
k8s_get_pod_logs; check previous logs when restart
count is greater than zero.
- Inspect owner references and describe the owning Deployment, StatefulSet,
DaemonSet, Job, or CronJob.
- Review events in the namespace with
k8s_get_events.
- Separate symptoms from root cause: restarts, failed probes, and unscheduled
pods are symptoms; the cause is the failing dependency, bad image, bad
configuration, resource pressure, or application error.
Output
Return:
- Pod, namespace, node, and owner
- Current phase and container waiting or termination reason
- Relevant log or event evidence
- Root cause
- GitOps-safe remediation