[pyrophane]

I don't think this is right. The reason I say that is because for the most part, teams new to k8s aren't building and managing their own clusters, they are using a managed solution. In that case, an application deployment only need be a few dozen lines of yaml. Most teams aren't really going to be building deep into k8s, and it shouldn't be hard to deploy your containers to some other managed solution.

[JackRabbitSlim]

Fair point, but then plenty of people were using hosted solutions for their naive PHP apps too. Managed solutions don't prevent poor/improper configuration in either case.

The managed hosts and/or their tools probably helped negate damage/resolve issues quicker. However I think that the idea that "all you need is a couple of dozen lines of yaml and a managed provider" is exactly why it's headed down a similar path.

For a real world examples just look at every improperly configured S3 bucket leaking data. Every private key accidentally posted to github from a careless 'git add -a'. Every API that doesn't properly check auth. None of these are within the purview of a managed hosts responsibility.

I'm not even against K8 in any of this. Just making the observation that - like PHP - it is empowering entire groups of people to do things they otherwise wouldn't be able to do.