Cecilie 🧙♀️Are there significant pros/cons between running #Kubernetes yourself on virtual machines in the cloud, versus using the cloud provider's managed Kubernetes service?
Asking as a 10-person team with 2-3 ops-y people on it.
mlbiam 
@cvennevik upgrades. I went from 1.24 -> 1.26 on eks with no down time in a couple of hours.
Tim Stoop @cvennevik My experience is that you'll start postponing upgrades more and more until it makes more sense to migrate to a new cluster. Not saying that's not a valid strategy, though.
Johannes Kastl@cvennevik Do you want to be responsible for the cluster and administer it yourselves? or do you only want to use it?
There might be some restrictions with manager clusters or some limits. But on the other hand less of an administrative burden...
@johanneskastl We need to run our services, and the cluster is a means to that end.
I get that there's a tradeoff, but I figured the benefits might still lean heavily in one direction or the other for our context.
Corvus@cvennevik using a Kubernetes cluster and administering one requires different expertise. Unless you have very specific requirements you can not get from your cloud provider of choice, then using a managed service is the more relaxed option.
If you can live with even more restrictions, then you can use a shared Kubernetes offering like for instance https://appuio.cloud (disclaimer: I am the product owner of APPUiO Cloud). Here you only have to care for what you put in your namespaces.
csbchristopher@cvennevik If someone breaks the control plane in a self-managed cluster, it can be complex to recover from it. This can happen for a few reasons, overloading, misconfiguration, etc.
Dealing with a managed control plane removes most of the hard parts from cluster management