What Kubernetes’ “monolith” lesson means for AI agent harnesses
Welcome to another edition of Road to KubeCon, your source for everything Kubernetes and cloud-native as we count down the The post What Kubernetes’ “monolith” lesson means for AI agent harnesses appeared first on The New Stack.
Welcome to another edition of Road to KubeCon, your source for everything Kubernetes and cloud-native as we count down the The post What Kubernetes’ “monolith” lesson means for AI agent harnesses appeared first on The New Stack.
In context
- Topic: Cloud y Arquitectura — Nube pública, híbrida, costos y decisiones de infraestructura.
- Source: The New Stack
- Published: 02/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
The cloud conversation moved from migrate everything to deciding what goes where. That maturity is a good sign, but it also makes the discussion harder: there is no single answer any more, it has to be argued case by case, and very few people have the numbers to do it.
I separate what moves for cost from what moves for capability. Migrating to save money almost never works; migrating to be able to do something you could not do before does. When the argument is only savings, it is worth checking the numbers again because they are usually incomplete.
What usually goes wrong
Where it usually breaks is team capability. The platform is new but people learned on the fly, with no time and no support. They end up replicating data-centre practices in the cloud, which means paying cloud prices for benefits that never arrive.
What to watch
- Three-year total cost with real growth, not the first-year promotion.
- How hard it would be to leave or move a piece to another provider, which is future negotiating power.
- Who sees the bill and in what detail: with no owner for the spend, the spend grows on its own.
How I read this entry
What I would install alongside any move to the cloud is the discipline of switching things off. Tag everything by owner, review monthly what is running unused, and give somebody the authority to turn it off. Without that, waste eats the promised savings within two years.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
