Problem Statement
You deploy a new version of your application and the Pods are stuck in Pending state indefinitely. What steps would you take to diagnose and resolve this? Include what you check in nodes, scheduling, storage and networking.
Explanation
First I would check the Pod description with `kubectl describe pod <name>` to view events: scheduling failures, resource insufficiency or volume mount errors. If “0/1 nodes are available” appears, I’d inspect node readiness with `kubectl get nodes` and `kubectl describe node <node>` for taints, conditions or resource pressure. Then I’d check storage: if the Pod requests a PersistentVolumeClaim, I’d validate the PVC and associated StorageClass, check if the PersistentVolume is bound and accessible. For networking, I’d ensure network-policy or CNI plugin is not blocking scheduling. If everything seems fine I’d check resource requests and limits in Pod spec; if requests are too high or limits too low, pods may not be scheduled. After identifying root cause I’d correct the spec or infrastructure and reapply the deployment. This scenario is common in real-world Kubernetes interviews, and handling it properly shows troubleshooting ability. :contentReference[oaicite:0]{index=0}
