Living with the Pathology of the Cloud: How AWS Runs Lots of Clusters
Talkat KubeCon + CloudNativeCon North America 2019 · on Tuesday, 2019-11-19· at 14:25· Room 29ABCD - San Diego Convention Center, Upper Level·
summary
EKS control planes run on public AWS primitives: API Gateway + Lambda front end, CloudFormation stacks per cluster, a dedicated VPC, NLBs, and managed node groups; etcd runs as three-node clusters per control plane with managed etcd backups and quorum monitoring. Operators hit a 15 minutes TCP stall caused by a Go HTTP/2 connection bug that left connections established, and a mutating webhook pushed p99 pod creation for 5,000 pods from ~5m to 46m; adding an in-memory cache restores sub-second P99s. Cellular architecture isolates rollouts into many shards to limit blast radius.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:14EKS Service Priorities
- 5:25Managed Node Groups
- 6:05Cellular Base Architecture
- 8:24Tradeoffs
- 10:02How is the cluster created
- 13:48Kubernetes learnings
- 20:18CD quorum
- 26:51Service accounts
- 29:01Data Path
- 32:26Lessons Learned
- 33:32Questions
related talks
35mKubernetes on AWS: Practices & Opinions
17mKeynote: Kubernetes: Lessons from the Trenches
17mKeynote: Kubernetes: Lessons from the Trenches
11mAmazon EKS Roadmap
27mRunning Kubernetes in Production A Million Ways to Crash Your Cluster
16mKeynote: Cloud Native at AWS
37mkubernetes on AWS gone wild
29mAmazon Elastic Container Service for Kubernetes (EKS): A case study - M. Re Ferre' and G. Carabelli
