Kubernetes won the orchestration wars. Its teams are still fighting.
Kubernetes won the container orchestration wars. The CNCF reports that 82% of container users run Kubernetes in production. Despite its The post Kubernetes won the orchestration wars. Its teams are still fighting. appeared first on The New Stack.
Kubernetes won the container orchestration wars. The CNCF reports that 82% of container users run Kubernetes in production. Despite its The post Kubernetes won the orchestration wars. Its teams are still fighting. 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: 07/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 stopped being a technical decision a long time ago. Today it is a financial decision with technical consequences: capital investment gets swapped for monthly spend, and that swap suits some companies very well and others very badly.
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
What I see fail most is the literal migration. The system gets moved exactly as it was, nothing redesigned, and you end up paying hourly for what used to be paid once. It works the same, costs more, and two years later somebody asks why it was done. Lift and shift is not modernising.
What to watch
- 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.
- Where the data physically sits and what local regulation demands about that.
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.
