article
Kubernetes is often organisational debt
Teams adopt orchestration to look mature, then spend scarce engineering time operating a platform their product did not require.
Emil Shirokikh · Published September 8, 2026 · Updated September 23, 2026 · 2 min read
Abstract
Kubernetes can solve real scheduling and isolation problems. Used prematurely, it converts simple deployment work into a permanent coordination and expertise burden.
Prove the scheduling problem
Kubernetes is powerful, but its control plane, upgrades, policy and observability become a permanent product the company must operate.
Platform comparison
Write down the scheduling, isolation and portability requirements. Compare a managed runtime and Kubernetes across people, recovery, security and three-year operating cost.
Release gate
Adopt orchestration when its specific capabilities outweigh the platform team it creates.
Challenge the conclusion
At sufficient scale or complexity, Kubernetes is an excellent foundation. The controversy is timing, not capability.
Use this in a working session
Ask who takes the 2 a.m. control-plane failure, who owns upgrades and which product requirement cannot be met by a simpler runtime.
BELTO editorial analysis. It does not describe a client engagement or claim a commercial result.
References
2 sourcesAuthor
Emil ShirokikhFounder
Founder of Belto Inc. Writes on engineering, venture building and applied intelligence.
Related
Read next
Most AI pilots should be killed sooner
The polite fiction around enterprise AI is that every pilot teaches something. Many teach only that nobody defined the decision, owner or failure cost.
AI agents need boundaries, not personalities
The market is decorating automation with human traits while neglecting permissions, reversibility and evidence.
A computer-vision demo is not a system
Benchmark accuracy says little about glare, drift, maintenance, latency or the operator who must act on an alert.