When Kubernetes costs more than it saves

A small team adopted a complex container platform for a handful of apps, and now spends much of its time running the platform. A simpler managed service can lower the total cost even if the bill barely changes.

2 min readMade-up stories, not client work

Cost Optimization: story 15 of 15

A made-up story

Picture a small software team that adopted Kubernetes, a powerful system for running many apps, because big tech companies use it. They run a handful of apps.

What's going wrong

Much of the team's week now goes into keeping the platform healthy instead of building the product. Upgrades are stressful, and only one person really understands it.

What they have today

  • A handful of apps on a self-run Kubernetes setup
  • One person who knows how it all works
  • Frequent upgrade chores

What we can't ignore

  • The product can't go down during a change
  • The team is small
  • Features are falling behind

The choices

  • Worth a look

    Hire a platform specialist and keep it

    Keeps the power, adds a salary.

  • Worth a look

    Switch to the provider's managed version

    Less upkeep, but still a complex system to understand.

  • Our pick

    Move to a simpler managed app service

    Apps run with far less upkeep, and anyone on the team can manage them.

  • Not for them

    Leave things as they are

    The hidden cost keeps growing.

What we'd do

Move the apps one at a time to a simpler managed service, starting with the easiest, shifting traffic gradually and keeping the old setup as a fallback until the last app is moved. Write everything down as code, then switch the old setup off.

Why

  • The team gets its time back
  • No single person holds all the knowledge
  • One app at a time keeps the risk small

Where the money really goes

No prices here: this shows where the costs sit, not what they'd be for any real business.

The monthly bill may barely change. The real saving is the team's time, and not needing to hire a specialist.

Hosting
Similar either way.
Team time
Far less upkeep with the simpler service.
Hiring
No specialist needed to keep it running.

Running, growing, and staying safe

If something breaks

The managed service handles restarts and updates, and each move has a fallback.

When it grows

Apps add copies automatically when busy.

Keeping it safe

The provider handles platform updates, so fewer things are left unpatched.

What the business gets

  • More time for the product
  • Less stress at upgrade time
  • A setup the whole team understands

These are the kinds of results the approach aims for, not measured results.

When we'd look again

If the company grows to many apps and teams with complex needs, a managed Kubernetes service would be worth reconsidering, with the right people in place.

If you liked this, read

About these stories. These stories are made up to show how we think. They are not client projects, describe no real business, and contain no measured results.

Next: Software that earns its keep: build what customers need first

Two short stories: launching something new, and fixing what already runs the business. Made-up examples of how we think, not client projects.

Read the next story