It makes sense to use full Kubernetes in that case. The lightweight distributions are good for single instances or limited multiple nodes. Like homelabs, edge nodes, or local development. But hosting application in data center makes sense to use full Kubernetes.
If you are in a datacenter, it's best to use the K8s distributed by that datacenter (EKS for AWS, for example).
The EKS provided by a datacenter will have integrations with external to Kubernetes resources you will almost certainly want (like storage, DNS records, or load balancers).
k3s and microk8s definitely support multiple node setup. I'm not sure about kind or minikube (Maybe? You'd have to look into the docs). How ready they are and how well they'll scale out will depend a lot on how the controllers are setup.
k3s, at least, supports multiple controller nodes on setup.
Where things really get squirrelly, at least with k3s, is storage and ingresses. k3s supports both but in a super robust fashion.
