DEVOURED
One pod, one node: The architecture behind serverless Kubernetes on AWS
AWS Fargate for EKS achieves serverless Kubernetes by providing a dedicated, isolated execution environment for every single pod.
What: Sri Saran Balaji (AWS) details how Fargate uses an admission webhook to route pods, a specialized scheduler to provision capacity, and direct VPC integration via ENIs to eliminate worker node management.
Why it matters: Fargate represents a move toward 'infrastructure-less' computing, shifting the operational burden from managing node fleets to configuring pod-level execution constraints.
Deep dive
- Admission Routing: Mutating webhooks force pods into a Fargate-specific scheduling path based on profiles.
- Scheduler: Replaces standard node-pool selection with an on-demand provisioner that allocates resources per pod.
- Networking: Each pod receives a dedicated ENI (Elastic Network Interface) within the customer VPC, eliminating cross-pod noise.
- Isolation: Uses a multi-namespace approach (Platform/Node/Workload) to secure credential vending and management traffic.
- Runtime: A managed kubelet is injected into the pod environment, providing standard API operations while limiting debug-flags.
Decoder
- ENI: Elastic Network Interface, a virtual network interface that represents a logical network card attached to an AWS instance or pod.
- Admission Webhook: An HTTP callback mechanism that allows modification or validation of Kubernetes API objects before they are persisted.
Original article
Full article content is not available for inline reading.
Explore all 54 articles in today's digest
Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi