[dns_snek]

I imagine the expectation is that the company obviously needs to know how to perform regular hardware maintenance, but the hypervisor/orchestration layer should be so well integrated that it doesn't require an expert team to operate (like you would need with a self-hosted Kubernetes cluster, which is notoriously difficult to understand and operate in production).

If that illusion breaks and you need to get into the weeds in the same way you do with self-hosted k8s, then the value proposition of their product goes poof. I'm just speculating, of course.

[Havoc]

> self-hosted Kubernetes cluster, which is notoriously difficult to understand and operate in production).

Yeah that was my reference point - cluster at home. Breaks often & hard and usually end up wiping it. Good for home use but I’d not want to rely on it for prod

[sgarland]

What distribution are you using? I’ve been running k3os (with etcd) for about two years without issues, other than Rancher Labs dropping support for it so it’s well past EoL.

[Havoc]

Vanilla K3s on a mixture of node types. Mostly ARM

It is a practice cluster though so I’m not exactly careful in my experimenting