Question

Users report that pods on node worker-2 are being terminated and rescheduled unexpectedly. Running 'kubectl describe node worker-2' shows the condition 'DiskPressure  True' and events indicating 'The node had condition: [DiskPressure]'. Several pods on that node show status 'Evicted'. What is the most likely root cause and appropriate first action?

Accepted Answer

The kubelet has crossed its eviction threshold for available disk space; investigate and free space on the node's filesystem (e.g., prune unused images/logs) or expand the disk.

Answer

The pods have invalid resource requests; edit each pod spec to lower CPU and memory requests so they can be rescheduled.

Answer

kube-proxy is misconfigured on worker-2; restart kube-proxy to clear the DiskPressure condition.

Answer

The control-plane scheduler is failing; restart kube-scheduler to stop the evictions.