well I did this as well that's why I'm pro k8s. heck setting up k8s and then deploying with that is certainly 1000 times easier than my ansible script was. worse my ansible script had a small downtime. k3s does not have that. the problem is a lot of people try to solve a problem with k8s that k8s does not solve. k8s is mostly a deployment scheduler with application configuration and an api for secrets. thats it.

it comes with an api for loadbalancer and ingress but it does not have one built in, but you can schedule these things with it. so basically even your low level primitives can be scheduled with the same api.