Kubernetes patches its three newest minor versions, then drops each one roughly a year after it ships [1]. PostgreSQL keeps a major version alive for five years and ships a fix at least every three months [2]. These clocks drive the hidden cost of running your own systems.

Cloud vendors now openly price the work of taking that clock off your hands: $0.10 per cluster-hour at Google Cloud, or a free control plane at DigitalOcean [4][5].

The big picture:

Every system a team runs inherits a support clock from the people who built it.

The software license is the visible cost of running it yourself. The fix calendar is the hidden tax that rarely hits a spreadsheet.

What strikes me is how tight some of these windows turn out to be.

I have watched this exact cost hit a team. One group built a custom tool to avoid a $20,000 yearly fee.

Over two years, three senior engineers spent 1,200 hours keeping that tool patched to match new cluster changes and to add single sign-on support. The team scrapped the tool in the end.

The clocks read the same in plain numbers. Kubernetes backs only its newest three versions, giving each about a year of patches [1].

PostgreSQL keeps a major version alive for five years, pushing fixes at least every three months [2]. Ubuntu’s long-term support (LTS) gives five years of standard security fixes, which stretches to ten or fifteen on paid plans [3]. Node.js promises 30 months of fixes on its LTS releases, and turns to an annual release cycle from version 27 [7].

Each of those windows sets how much of a senior engineer’s year a layer will take.

By the numbers

  • Three minor versions — Kubernetes’ window: The project backs only the three most recent minor versions, giving versions from 1.19 onward roughly one year of patches [1].
  • 5 years — PostgreSQL’s clock: PostgreSQL supports a major version for five years from release, shipping minor fixes at least once every three months [2].
  • $0.10 — Google’s fee: Google Cloud charges a flat $0.10 per cluster-hour for a managed control plane, offering $74.40 in monthly free credit [4].
  • $65.38 — Developer hourly pay: The 2025 middle hourly pay for software builders sits at $65.38 [6]. Google’s $73 monthly fee equals about 1.1 hours of an engineer’s time.

What I’d watch:

Cloud vendors now price this patch work openly, and the models are worth comparing.

  • The per-cluster fee: Google charges a flat $0.10 per cluster-hour no matter the size, then hands back $74.40 a month in credit [4].
  • The free control plane: DigitalOcean gives the managed control plane away for free, charging $40 a month only for the high availability (HA) version [5]. That is the same product class priced two different ways.
  • The clock sold by the year: Canonical stretches Ubuntu’s five years of standard fixes to ten or fifteen years with a paid plan [3].
  • The window that moved: Kubernetes stretched its patch window from nine months to about a year at version 1.19 [1].

My read is that teams handling this well track a list of clocks, not just a list of licenses. They map one row per system layer with a specific owner beside each fix cycle.

The catch

A support clock is not the entire bill.

Buying a managed control plane stops one treadmill, but it leaves workload fixes, data moves, and app changes on the team’s plate [4][5].

Free tiers cut both ways. DigitalOcean offers a free control plane, and Google’s credit covers a small cluster, but a low fee alone is a weak reason to move a workload if the managed tier cannot run it well.

The $65.38 wage figure is a national middle point, which hides a wide spread by role and region [6].

The part I keep circling is that these clocks are rules, not physics. Kubernetes already changed its window once [1]. The release calendar is the first thing I would check before committing to a self-hosted tool for more than a year.

At a glance

  • The Big Shift: Every system layer a team runs in-house arrives with an upstream patch clock driving its fix schedule.
  • Why It Matters: The license fee is the visible cost; the fix calendar is the hidden one. Vendors now price that calendar in the open, from $0.10 per cluster-hour to a free control plane.
  • What I’d Watch: How vendors package the fix clock and whether open-source projects shorten or stretch their windows.
  • The per-cluster fee: A flat hourly charge for a managed control plane, keeping the price the same no matter the cluster size.
  • The free tier: Monthly credit that offsets a small cluster’s fee, dropping the real price near zero.
  • The subscription ladder: Paid plans that stretch a free project’s security window from five years out to fifteen.
  • The Catch: Buying a managed tool only covers part of the bill, leaving workload fixes, data moves, and operator wages on your side of the ledger.

Related reading

Sources

[1] Kubernetes — “Releases” (release history and support policy): https://kubernetes.io/releases/ [2] PostgreSQL Global Development Group — “Versioning Policy”: https://www.postgresql.org/support/versioning/ [3] Canonical — “Ubuntu release cycle” (security and support coverage): https://ubuntu.com/about/release-cycle [4] Google Cloud — “Google Kubernetes Engine pricing” (cluster management fee, free tier, uptime promise): https://cloud.google.com/kubernetes-engine/pricing [5] DigitalOcean — “Kubernetes pricing” (free control plane, high-availability option): https://www.digitalocean.com/pricing/kubernetes [6] O*NET OnLine — Software Developers (15-1252.00), median wages 2025: https://www.onetonline.org/link/summary/15-1252.00 [7] Node.js — “Releases” (previous releases and long-term support policy): https://nodejs.org/en/about/previous-releases