Kubernetes is our generation's Multics
The problem is the devops culture that has burdened development teams with having to juggle a lot of complexity. The solution is having some separation of concerns. Development teams should not have to spend a lot of time on devops. That&#x27;s something that should just work that you buy from someone. You pay for the privilege of doing more interesting things.<p>Kubernetes becomes a problem when you have people who are not operations people with many years of experience with this stuff trying to do this while learning how to do it at the same time. The related problem is that having people spend time on this is orders of magnitudes more expensive than it is to run an actual cluster, which is also not cheap.<p>A week of devops time easily equates months&#x2F;years of cloud hosting time for a modestly sized setup using e.g. Google Cloud Run. And lets face it, it&#x27;s never just a week. Many teams have full time dev ops people costing 100-200$K&#x2F;year, each. Great if you are running a business generating millions of revenue. Not so great if you are running a project that has yet to generate a single dollar of revenue and is a long time away from actually getting there. That describes most startups out there.<p>I actually managed to stay below the Cloud Run freemium layer for a while making it close to free. Took me 2 minutes to setup CI&#x2F;CD. Comes with logging, auto scaling, alerting, etc. Best of all, it freed me up to do more interesting things. Technically I&#x27;m using Kubernetes. Except of course I&#x27;m not. I spent zero time fiddling with kubernetes specific config. All I did was tell Google Cloud run to go create me a CI&#x2F;CD pipeline from this git repository and scale it. 3 minute job to click together. Service was up and running right after the build succeeded. Great stuff. That&#x27;s how devops should be: spend a minimum of time on it in exchange for acceptable results.