~/talk

Why should you bother about cluster autoscaling- Karpenter

Talkat Conf42 Cloud Native 2022 · 2022-04-28..04-29· [kubernetes, serverless]
linkedin:rajasganesan
slides:none on file

Karpenter claims to provision nodes directly by calling cloud compute APIs (example AWS EC2 Fleet) instead of expanding ASGs, and it picks the smallest set of instance types that fit pending pods (m5.xlarge instead of matching t3.mediums in the demo). It prioritizes spot instances and falls back to on‑demand, uses ttlSecondsUntilExpired and node‑empty TTLs to delete nodes, and binds pods during provisioning so images can prepull — all aimed at faster, groupless scaling and lower retry latency.

AI-written summary · about

  1. 0:00Karpenter intro
  2. 2:52Why cluster autoscaling matters
  3. 3:36How Cluster Autoscaler works
  4. 8:38Karpenter intro
  5. 9:41How Karpenter provisions nodes
  6. 13:33Karpenter with provisioners
  7. 15:19Spot and on-demand mix
  8. 16:43Karpenter operations
  9. 17:46Single vs multiple provisioners
  10. 19:31Topology spread constraints
  11. 19:53Karpenter advantages
  12. 21:20Q&A
~/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.