The New Stack: One pod, one node: The architecture behind serverless Kubernetes on AWS
The article walks through how Amazon EKS Fargate places a pod: a mutating admission webhook assigns it to a Fargate scheduler before the default scheduler can claim it, the scheduler requests dedicated capacity, and a node runtime registers the pod's environment. It also describes three network namespaces, one ENI per pod, and EKS periodically replacing pods for security patching via the Eviction API. The piece is an architectural explainer and does not announce a new release.
What changes for platform teams
Platform teams using Fargate should plan for one ENI and private subnet capacity per pod, a pod-level patching cycle that respects PodDisruptionBudgets, and the lack of DaemonSets, host networking, EBS volumes and GPUs. Every pod must match a Fargate profile.
Read the original at The New Stack ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules