[mrweasel]

While I don't know who Kubernetes was built for, it's certainly developers who are pushing for Kubernetes.

The majority of SREs and sys admins I know don't really want to run Kubernetes. They'll do it, if that's what's called for, but it just adds complexity to trivial problems.

Developers want Kubernetes because it's quick to deploy containers, networks, load balancers, anything they want. That's fair, traditional hosting doesn't have much that provides that level of flexibility or that will allow you to get off the ground at that speed.

The issue is that as a platform Kubernetes isn't that easy to manage. It certain has improve, but it can be difficult to debug when it break. Nobody wants a 3AM page that a Kubernetes cluster is down. We've even seen companies say that they'll just stand up a new cluster if something breaks, because it's faster. Add to that the complexity of components deployed inside your cluster. As an SRE it absolutely suck to get the "hey the network's broken" from a developer, because that means that you now have to be an expert on WHATEVER load balancer or CNI they've decides to pull in.

As great as much of the stuff you can deploy in Kubernetes is, it's still harder to debug than an application running on a VM or bare metal server, with a "real" network.

[jmillikin]

  > Developers want Kubernetes because it's quick to deploy containers,
  > networks, load balancers, anything they want.
  > [...]
  >
  > As an SRE it absolutely suck to get the "hey the network's broken"
  > from a developer, because that means that you now have to be an
  > expert on WHATEVER load balancer or CNI they've decides to pull in.

This is why the "DevOps" approach exists.

If a developer wants root in the cluster so they can deploy some strange low-level plugin, then they need to be the ones carrying the pager.