[Runamok81]

As a counterpoint from my own personal experience, time spent managing kubernetes is time NOT spent introducing new features.

I once had the displeasure of watching an upstart data science team at a boutique portfolio management firm break under the weight of k8s management. The team was great at critical thinking, risk-modeling, and statistical analysis. They knew very little about infrastructure, such as networking fundamentals or CPU/Memory management. This team went from helping our firm rapidly develop a sentiment analysis model that sifts through social media for trading signals to wrestling with kubectl all day. Productivity bombed. Team was disbanded about a year after they started using k8s.

It's a shame the author emphasized and inflated the discrete costs of operating a cluster because that emphasis and exaggeration distracts from the TRUE cost ... opportunity cost. We want our engineering teams doing what they do best, writing code and adding new features. Not bogged down in managing the plumbing/infrastructure. Happy to have that abstracted away.

[icedchai]

Sounds like they needed an ops person, sysadmin, etc. This is nothing new: Most developers are not good at being sysadmins.

[dilyevsky]

Just wait until an upstart sysops team will try to ship some trading software