Menu

The EKS cost playbook: 7 levers we pull on every audit
πŸ“°

The EKS cost playbook: 7 levers we pull on every audit

DEV Community: kubernetesΒ·Unified TechsΒ·about 3 hours ago
#O24KCRSF
#devtokubernetes#devto#dev#spot#cost
Long article (350 words) β€” no AI summary yet.
Reading 0:00
15s threshold

On every EKS cost audit we run, the same handful of levers explain 80% of the savings. None of them are clever. All of them are deferred because they require coordination across application, platform and finance teams. Here's the short list, in roughly the order we apply them.

1. Right-size requests, not limits

CPU and memory requests are what the scheduler reserves. Most teams set them by copy-pasting from another service that was already wrong. Pull actual usage from Prometheus over a representative two-week window and resize to the p95 plus a margin. This single change typically reclaims 20–30% of cluster capacity.

2. Replace the cluster autoscaler with Karpenter

Karpenter picks instance types per pending pod rather than scaling a fixed node group. The result is denser packing, faster scale-out and access to a much wider menu of instance shapes. We see 15–25% additional savings on top of right-sizing.

3.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.