The big detail that's going to affect what's right for production is how much information security matters to you.
Kubernetes lets you have mechanisms (ResourceQuota, LimitRange, Pod security admission, pod priority, …) that protect apps in one namespace from being affected by another namespace.
If you already know how to set these up - or you know that you'll have to learn them - then putting the apps onto control plane nodes of a ”regular” Kubernetes cluster can be a good fit.
That focus on infosec is going to make it important that you take appropriate hardening measures, and these are easier to do when the Kubernetes cluster you're configuring starts off like vanilla upstream Kubernetes.
You might even want to set up gVisor to provide additional restrictions on what the application containers can do. If that's a story that's important for your context, have a look at the CKS syllabus to learn about other topics to consider.
If information security isn't a big focus, and perhaps you're keen to get something up and running soon, I think k3s would be a better fit. k3s does more for you out of the box, and makes it easier to run a replicated control plane with good availability.