We moved 12 microservices off Kubernetes and our bill dropped 60%

Cloud Computing & SaaSTechdiscussion

We ran a 3-node managed cluster for eighteen months because that is what everyone said to do. Looking at the actual numbers, eleven of our twelve services handled under 5 requests per second at peak. What we changed: • The two services that genuinely need to scale stayed on Kubernetes. • Everything else moved to a pair of load-balanced VMs behind a process manager. • Cron jobs became actual cron, not CronJob objects. Monthly infra went from around ₹58,000 to ₹23,000. Deploys got slower to set up but faster to reason about — no more debugging why a pod was Pending at 2am. The honest trade-off: we gave up automatic bin-packing and rolling deploys with no downtime. For a team of four, that was worth it. If you are twenty engineers with fifty services, ignore all of this. Curious whether anyone here has gone the other way and regretted it?

Log in to join the conversation.

All Comments

No comments yet. Be the first to reply.

Haven’t Added a Project Yet?

Show real work, get validated by industry experts, and get discovered.

Add Project