~/talk

Resource Requests and Limits Under the Hood: The Journey of a Pod Spec

name:Kohei Ota
links:none on file
slides:none on file

Explains how a Pod spec flows: requests are recorded in etcd, scheduler uses them to pick a node, kubelet hands pod to the CRI runtime which sets cgroups; limits turn into cgroups values and CPU limits map to CFS period/quota (default 100ms so 500m → 50ms, 2000m → 200ms) and memory over-limit triggers the OOM killer. Covers QoS classes (Guaranteed, BestEffort), CPU shares vs request semantics, and VPA modes off/initial/auto and requests are for planning limits are for enforcement.

AI-written summary · about

  1. 0:00Intro
  2. 1:28Doggy Daycare Analogy
  3. 2:36Here's an ordinary pod spec
  4. 3:21Requests for planning
  5. 4:06Update Cluster State
  6. 5:15Scheduler
  7. 5:47Create Pod on Node
  8. 5:59The Journey of a Request
  9. 6:30Requests passing through
  10. 7:09Requests summary
  11. 7:56QoS Class in Kubernetes
  12. 8:44Now let's talk about limits
  13. 9:01Limits enforce.
  14. 9:36Assign Pod to Node
  15. 10:15Kubelet to Container Runtime
  16. 10:51Limits summary
  17. 11:55Limits by level
  18. 13:08Container Primitives
  19. 15:54CFS Quota? Period?
  20. 17:13CRI Runtime vs OCI Runtime
  21. 18:54Pod Autoscaling
  22. 19:42Vertical Pod Autoscaler (VPA)
  23. 22:21Conclusion
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.