Work / Case study
20–70%
cloud cost reduction range
Co-created Smart Karpenter: 20–70% Kubernetes cost reductions
01 / The receipt
- Cost reduction range
- 20–70%
- Partner
- Avesha
- Companion workshop
- authored
- Role
- Co-creator and workshop author
- Stack
- KubernetesKarpenterAWSEKSCost optimization
02 / THE PROBLEM
Kubernetes clusters are routinely over-provisioned: nodes sized for peak, bin-packing left to defaults, and spot capacity unused because nobody trusts the interruption story. The waste compounds quietly until the cloud bill becomes a board question.
03 / THE WORK
With Avesha, Zohaib co-created Smart Karpenter — intelligence on top of Karpenter’s node provisioning that right-sizes capacity against actual workload behavior, blends spot safely, and makes consolidation decisions a platform team can audit.
He then wrote the official hands-on workshop so platform engineers can reproduce the results on their own clusters — the same teaching-first approach Khavion brings to every engagement handover.
04 / THE RESULT
Cost reductions across teams applying the approach range from 20% on conservatively tuned clusters to 70% where over-provisioning was worst. The range is honest: your number depends on how much waste you start with, and an audit tells you that before you commit.
05 / WHAT WE’D PRESSURE-TEST IN YOURS
The 20–70% range isn’t a hedge — it’s the honest answer to “how much waste do you start with?” Before quoting a number for your clusters, we audit current provisioning, bin-packing, and spot posture: a conservatively tuned cluster lands near the bottom of the range, a badly over-provisioned one near the top.
The reproducible part matters. Because the approach is taught in the official hands-on workshop, your platform team can audit every consolidation decision instead of trusting a black box.
06 / Outcome
Want this kind of receipt for your own project?
Book a 30-minute fit call — or run the free assessment first to see whether a build like this is even the right move for you.