And that's actually my concern with K8s still. It still has an unnecessarily high maintenance burden for projects that are limited in scope and few scalability requirements. Which can often still be an important project.
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.
Kubernetes will still work after a year too, it just won't be supported. I forgot about a K3s setup for well over a year...
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.