A Deployment’s Pods stay Pending or fail image pulls. Which kubectl…

Question

A Deployment’s Pods stay Pending or fail image pulls. Which kubectl view best surfaces the Events explaining scheduling or image errors?

Accepted Answer

kubectl describe pod (or the Pod via the Deployment) and read the Events section. — When a Pod won’t start, the story is usually in Events—‘FailedScheduling,’ ‘ImagePullBackOff,’ and friends. kubectl describe pod puts those Events front and center. Read them before you start changing unrelated cluster knobs.

Answer

kubectl attach to a running etcd Pod and read raw WAL files.

Answer

kubectl config view --minify exclusively, ignoring the workload.

Answer

kubectl label nodes at random until Pods schedule.

A Deployment’s Pods stay Pending or fail image pulls. Which kubectl view best surfaces the Events explaining scheduling or image errors?

Short Explanation

Full Explanation