Menu

Kubernetes Cost Optimization for a 200-Node EKS Cluster
📰

Kubernetes Cost Optimization for a 200-Node EKS Cluster

DEV Community: kubernetes·DevOpsInterview.Cloud·13 days ago
#hjbeFGxo
#devtokubernetes#devto#dev#node#spot
Reading 0:00
15s threshold

"We run a 200-node EKS cluster with about 400 microservices. The bill is out of control, and the VP of Engineering wants it cut by 40 percent without hurting reliability. Walk me through your approach." This is a common senior Kubernetes cost optimization interview question, and the weak answer is "right-size the pods", which is too vague to act on. Interviewers want an order of operations: measure first, take the low-risk wins, then make the architectural changes, and explain the trade-off at each step.

The video version covers the same scenario if you prefer to watch it:

Why do resource requests drive Kubernetes costs?

The scheduler places a pod by comparing the requests already on a node against that node's allocatable capacity. What the pods actually use plays no part in the decision.…

Continue reading — create a free account

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