Scaling Kubernetes Workloads with Node Swap

What happened

Kubernetes (software that runs and manages applications across many servers) support for running nodes with swap enabled reached General Availability in v1.34, and by backing that swap with fast NVMe solid state drives (SSDs), a node can page out dormant memory and pack in far more pods. The node density problem The Kubernetes ecosystem has reached a fundamental physical resource constraint: the strict limits of hardware memory versus the growing demand for dynamic, bursty workloads in the new agentic (AI that carries out multi-step tasks rather than answering one question) era.

Memory is often the first hard limit a Kubernetes cluster hits. Nodes run out of RAM long before they run out of CPU (the general-purpose processor at the centre of a computer), and the new wave of agentic AI workloads makes this worse.

These workloads demand large memory footprints to start up and run untrusted code, then sit idle waiting for the next prompt. That idle but resident memory is expensive, and it caps how many pods a node can hold.