Often I find that a load balancer and a couple of docker compose file sis more rugged, because you'll be able to leave it for a year and it'll still work and easily be understood by just glancing at it.
If you don't need a cluster then a single node K3s is still better than Docker Compose. You might know how an ad hoc load balancer and Docker Compose works, but I wouldn't say this knowledge is any more given than knowing K8s these days.
But if you do need a cluster then maintaining a bunch of Talos nodes is easier than maintaining a bunch of full fat GNU/Linux boxen tbh.
I feel like k8s is better as soon as your thing goes from simple self-contained thing to multiple things running on one box
especially with agents it's never been easier to work with k8s.
from my experience, k3s supports basically everything k8s has that you'd need for a single-node setup
not sure what "Would k3s handle the proxy layer" means but if you mean the load-balancing part, then yes, that's like one of the main abstractions that k8s provides. but again, it provides many knobs so you probably just wanna pick the simplest option available
Yeah that's what I thought. Perhaps just put HAProxy in front and then let k3s know about it?
or use the Gateway/Ingress abstractions that basically do this automatically, where you just expose services via them, and they handle the routing
looks like the above is documented at: https://www.haproxy.com/documentation/kubernetes-ingress/
the nodeport way would basically be what you'd do with compose, where you map the host (node) ports to the container ones
For load balancing across a proper cluster then you can either provision an external load balancer (like keepalived) or you can look into something like MetalLB which runs entirely on-cluster (but you need BGP support for true load balancing).
In a cloud cluster (like AWS EKS) you get load balancers automatically just by provisioning a LoadBalancer type Service in Kubernetes.