Why should you bother about cluster autoscaling- Karpenter
summary
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
chapters (12)
- 0:00Karpenter intro
- 2:52Why cluster autoscaling matters
- 3:36How Cluster Autoscaler works
- 8:38Karpenter intro
- 9:41How Karpenter provisions nodes
- 13:33Karpenter with provisioners
- 15:19Spot and on-demand mix
- 16:43Karpenter operations
- 17:46Single vs multiple provisioners
- 19:31Topology spread constraints
- 19:53Karpenter advantages
- 21:20Q&A
related talks
36mGroupless Autoscaling with Karpenter
27mScaling K8s Clusters Without Losing Your Mind or Money
01h 01mJust-in-time Nodes for Any AWS EKS Cluster: Karpenter
22mKarpenter Efficient scaling of Kubernetes clusters
27mHarness the power of Karpenter to scale, optimize & upgrade K8s
22mUse Karpenter to scale, optimize & upgrade K8s
19mJust in time Worker Nodes with Karpenter
18mKarpenter : Your trusted Companion for Kubernetes Scaling
