Kubernetes and co do not reduce the amount of work - it’s just shifted to the next abstraction layer. Before when DevOps meant „you build it - you run it“ we removed dedicated ops teams to which the code was thrown over the fence and to reduce the animosity and friction between dev and ops. This was great but now all the hips companies have dedicated ops teams only that they are now called „platform teams“. Instead of code artefacts it is now containers that are thrown over the fence and now the ops part became so complex that separating dev and ops again seems reasonable. Luckily for me I managed to keep the good old DevOps of working, developing code and running it or bare metal servers with FreeBSD and Jails - even converting an existing Kubernetes setup back to bare metal. In my opinion the platformisation of the internet infrastructure isn’t a desirable state, monocultures are too and for the vast majority of projects kubernetes is overkill as they won’t ever reach the scale that would justify a kubernetes setup. It‘s like the milage fear for EV cars - but I guess everyone wants to hit facebook or google scale and that desire misinforms the early infrastructure architecture. That is just my 40 years old grey beard view which you can happily ignore whilst flying amongst the clouds :)