One Pod, One Node: The Architecture Behind Serverless Kubernetes on AWS
The New Stack, Tuesday, October 27th, 2026
How AWS Fargate gives every Kubernetes pod its own node, from admission webhooks and per-pod ENIs to patching via the Eviction API.
AWS Fargate makes the pod the unit of infrastructure, giving each pod a dedicated compute environment and a network interface in the customer's VPC that disappears when the pod ends.
An admission webhook routes matching pods to the Fargate scheduler before the default scheduler can claim them, and a runtime image matched to the control plane supplies the kubelet and node components.
EKS replaces Fargate pods for security patches through the Eviction API, respecting PodDisruptionBudgets.
DaemonSets, host networking, privileged pods, GPUs, HostPath and EBS volumes are unsupported, with EFS as the shared storage pattern.