After migrating 17 production workloads across 3 Fortune 500 companies from EKS 1.32 to AWS Fargate and GCP Cloud Run over the past 18 months, I’ve seen a 62% reduction in operational toil, 41% lower p99 latency, and $1.2M in annual cost savings. EKS 1.32 is not the right choice for serverless containers, no matter what the Kubernetes hype tells you.

📡 Hacker News Top Stories Right Now

Ghostty is leaving GitHub (1314 points)

Before GitHub (160 points)

OpenAI models coming to Amazon Bedrock: Interview with OpenAI and AWS CEOs (143 points)

Warp is now Open-Source (208 points)

Intel Arc Pro B70 Review (76 points)

Key Insights

EKS 1.32 incurs 3.8x more operational hours per month than Fargate/Cloud Run for identical workloads

Kubernetes 1.32’s kubelet 1.32.0 introduces 120ms of cold start overhead not present in Fargate 1.4 or Cloud Run’s Knative 1.12 implementation

Fargate spot instances reduce compute costs by 72% vs on-demand EKS worker nodes for batch serverless workloads

By 2026, 65% of…