KubernetesSenior

Pods evicted by node pressure (MemoryPressure, DiskPressure, PIDPressure)

When a node runs low on memory, disk or process IDs the kubelet evicts pods. Read the node conditions and set thresholds, requests and limits to match.

What you see

  • Pods are terminated on a node and their phase is Failed
  • The node reports MemoryPressure, DiskPressure or PIDPressure

What it means

The kubelet watches resources such as memory.available, nodefs.available, imagefs.available and pid.available. When one crosses an eviction threshold it first tries to reclaim node resources, for example by removing unused container images when disk is short. If that is not enough it evicts pods.

During a node-pressure eviction the kubelet sets the phase of the chosen pods to Failed and terminates them. It does not respect a PodDisruptionBudget or the pod's terminationGracePeriodSeconds. For hard thresholds it uses a 0s grace period, so shutdown is immediate. Pods managed by a Deployment or StatefulSet are replaced by the control plane.

How to confirm the cause

  1. 1
    Check the node's conditions
    kubectl describe node NODE_NAME

    Look at Conditions for MemoryPressure, DiskPressure and PIDPressure.

  2. 2
    See what is running on the node and what it requests
    kubectl describe node NODE_NAME

    The Non-terminated Pods and Allocated resources blocks show who is using the node.

Causes and fixes

  • Memory pressure

    HOW TO TELL
    MemoryPressure is True. The signal is memory.available.
    FIX
    Set memory requests and limits so pods fit, spread load across more nodes, or add memory. Pods using more than they requested are evicted before those within their requests.
  • Disk pressure

    HOW TO TELL
    DiskPressure is True. Signals are nodefs.available, nodefs.inodesFree, imagefs.available and similar.
    FIX
    The kubelet first garbage collects dead pods and containers, then unused images. If that is not enough, find what is filling the node's filesystem, using the Linux disk-full runbook.
  • PID pressure

    HOW TO TELL
    PIDPressure is True. The signal is pid.available.
    FIX
    Find the workload creating too many processes and cap it.

How to stop it coming back

  • Set requests and limits on every pod so eviction order is predictable.
  • Alert on node conditions before the kubelet starts evicting.
  • Give critical pods a high priority class.

Keep going

Sources

Kubernetes documentation (kubernetes.io), read 18 Nov 2026. The docs version selector listed v1.33 to v1.37.

Search

Search cheat sheets and projects