K8S doesn't scale nearly as well due to etcd and latency sensitivity. Multi-site K8S is messy. The whole K8S model is overly-complex for what almost any org actually needs. Proxmox, Incus, and Nomad are much better designed for ease of use and large scale.
That said, I still run K8S in my homelab. It's an (unfortunately) important skill to maintain, and operators for Ceph and databases are worth the up-front trouble for ease of management and consumption.
multi-site k8s is also very "interesting" if you encounter anything like variable latency in your network paths. etcd is definitly not designed for use across large distances. (more then a 10km single mode fiber path).
Maintaining an external database as a replacement takes you off the blessed path, is it's own hassle to maintain high availability, and tarnishes the shiny hyperconvergance story. I'd be a lot more interested if Kine offered an embedded HA database like YugabyteDB, CockroachDB, TiDB, etc.
That said, I still run K8S in my homelab. It's an (unfortunately) important skill to maintain, and operators for Ceph and databases are worth the up-front trouble for ease of management and consumption.