Kubernetes solves real problems for the 1% who need it. The other 99% are paying a massive complexity tax for capabilities they never use, while 87% of their provisioned CPU sits idle.

is where the author is just wrong:

- abstracts away ssh - makes it pretty unnecessary

- rbac multi tenancy

- better automations

- orchestating more than one cluster

- better infra as code

- provisions are as good as you make them, if you don't want them only use limits.

- large mind share, bitnami (was) great

I use k3s for my home network because it's simple and easy, thinking that k8s is overengineered just plain wrong - it's just different especially if you compare different versions of k8s designed for different things where for ex: k3s bundles csi, cni, ctl, ingress for you.

I actually struggle with compose ('orchestration' alternative) significantly more since it usually has complicated workarounds to missing features.

I have been running 5 k8s-flavored clusters for more than half a decade between 1 to 40 nodes.