Diagnose Kubernetes pod scheduling failures from kubectl describe pod events.
npx skills add https://github.com/scitix/siclaw --skill pod-pending-debug
Please help me install this Agent Skill. Skill: pod-pending-debug Source: https://github.com/scitix/siclaw/tree/main/skills/core/pod-pending-debug Command: npx skills add https://github.com/scitix/siclaw --skill pod-pending-debug
This Skill helps diagnose and understand why a Kubernetes pod is stuck in a Pending state, preventing it from being scheduled onto a node.
kubectl describe pod events to pinpoint FailedScheduling reasons.Use the pod-pending-debug skill to diagnose why the pod named 'my-app-pod' in the 'development' namespace is pending.
High-intent search queries and answers about installing and using this skill.
Kubernetes pods remain Pending due to scheduling failures like insufficient node resources, affinity mismatches, taint conflicts, or unbound PVCs. This skill diagnoses these exact failures by analyzing pod events and node constraints to pinpoint the specific scheduling block.
Debug a FailedScheduling event by parsing `kubectl describe pod` output to verify node resources, taints, and PVC bindings. This skill analyzes those events and checks cluster node conditions against your pod requirements to identify the scheduling failure.
Pods remain Pending when cluster resources are insufficient or pod constraints cannot be met. This skill checks for insufficient resources, incorrect node selectors, affinity rule mismatches, taint/toleration conflicts, and unmet persistent volume claim dependencies.
Yes, this skill diagnoses Pending pods caused by unbound persistent volume claims. It verifies PVC bindings alongside node resources, taints, and affinity rules to determine if storage dependencies are preventing successful pod scheduling.
Check node taints by comparing them against your pod's tolerations using `kubectl describe pod` events. This skill evaluates taint/toleration conflicts alongside affinity rules and resource limits to identify why the scheduler rejects your pod.
Sir-chawakornDiagnose Kubernetes workload failures by analyzing pod status, events, logs, and node constraints.
ivanshamaevDiagnose Kubernetes cluster health issues from node, pod, and control-plane evidence.
cnoe-ioQuery EKS clusters via kubectl and report pod, node, and resource health.
tedtv1007-ctrlDeploy, scale, and troubleshoot containerized applications in Kubernetes clusters.