What surprises people first about a startup's Kubernetes bill is how predictable the leaks are. Across the small-team AWS and GCP bills we audit, the same seven patterns drive 70 to 90% of the waste, and they're all fixable in a single quarter.

This post is the consolidated playbook. It covers the seven patterns, the realistic savings on each, and the structural change that keeps them from drifting back: making the platform carry the defaults.

Skim answer:

The seven highest-leverage patterns: right-sizing, spot capacity, idle environment sleep, namespace quotas, image-pull traffic reduction, NAT-routing audits, and storage class right-sizing.

Combined impact: typically cuts a small-team Kubernetes bill by 40 to 65%.

Timeline: all seven are fixable in a single quarter.

Why startup K8s bills are usually 2x what they should be

The math behind the typical waste:

Most teams set resource requests at 2x to 4x what the workload actually uses, "to be safe".…