~/talk

Resize Your Pods In-Place With Deterministic eBPF Triggers

links:none on file
links:none on file
slides:none on file

Demonstrates a concrete system that detects a build command and expands a running pod’s resources without restart by combining Kubernetes’ upcoming in-place pod resize API (APIserver/kubelet/CRI changes, containerd update_container_resources) with an execve eBPF trigger that monitors cgroup IDs and command names via BPF maps and a DaemonSet. Prototype raises memory to 5 GiB on make, turns tens-to-hundreds-second VPA reactions into sub-second resizing, and works in demo though code is a proof-of-concept.

AI-written summary · about

  1. 0:00Intro
  2. 1:29The End of Local Development
  3. 3:59The Dawn of Cloud-Native Development
  4. 6:07Cost Reduction
  5. 7:32Booting Spikes + VPA + In-Place Pod Resize
  6. 8:36"make" Spikes + VPA + In-Place Pod Resize
  7. 9:38Optimal "make" Spikes Behavior
  8. 12:09In-Place Pod Resize - What Changed?
  9. 14:59In-Place Pod Resize - What Does It Involve?
  10. 15:44In-Place Pod Resize - Design
  11. 17:54In-Place Pod Resize - Container Resize Order
  12. 19:03In-Place Resize - Expectations From Runtime
  13. 20:26In-Place Pod Resize - Innovating with eBPF
  14. 23:19In-Place Pod Resize + eBPF + BPF maps
  15. 30:29Key Takeaways
~/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.