Kubernetes Scalability Definition Evolution
summary
Kubernetes starts with a 100-node claim in 2015 but proves it insufficient, replacing vague thresholds with explicit SLIs/SLOs: original rules (API responsiveness 99% <1s, pod startup 99% <5s) expose poor coverage and precision, so a 2017 product-surface doc and the concepts of scalability dimensions and scalability envelope emerge. Current official SLOs cover mutating/read API latency and pod startup with a 5,000-node limit, use per-resource streams and 99th percentile over 5 minutes, and several networking/storage SLIs remain "working progress" measured in synthetic benchmarks.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:20Scalability - what does it mean?
- 4:10Scalability - how to define it?
- 6:11Definition drawbacks
- 8:48Scalability SLOs - coverage
- 10:52Scalability - SLOs coverage
- 12:58SLISLO principles
- 16:27How to provide SLOs?
- 17:53Defining Kubernetes limits
- 18:50Scalability SLO framework
- 26:48Defining Scalability
- 29:02Current state
related talks
01h 05mIntro + DeepDive: SIG Scalability
43mIntro + Deep Dive: SIG Scalability
25mAn SLO-Driven Approach to Enhance Kubernetes Cluster Reliability
29mIntro + DeepDive: SIG Scalability
34mPanel: Improving and Managing Kubernetes at Scale
42m2000 Nodes and Beyond: How We Scaled Kubernetes to 60,000-Container Clusters
48mScale and Performance Testing of Kubernetes: Answers for Specific Applications
50mScale Kubernetes to Manage 60K Nodes Through Architectural Extension
