@HerraBRE
Why do you need convincing? Choose the method that you are most comfortable with.

@HerraBRE What are you expecting form #Kubernetes?

Kubernetes is a completely different way of building and managing your infra.

For example, I switched my #homelab from VMs to K8s 2 years ago because I wanted a GitOps approach, immutability, easy observability, L2 load balancers, advanced network policies up to L7, Mesh, HA, and so on.

You can achieve the same with Linux & Containers, but Kubernetes gives you a standardized and opinionated way of doing it.

You LOVE it or HATE it.

@HerraBRE take a look at the Gateway API. This is the thing to replace ingress and it explicitly was built to also support TCP/UDP. Using this myself, it works.

@HerraBRE #kubernetes works fine for any services that use TCP or UDP. It's just an orchestration API. Whether you should use it is a question of scale, mostly. In the past decade, I've put all sorts of things on #K8S.

@HerraBRE I’d say your gut is correct but what are they exactly?

@HerraBRE what exactly do you want to run in k8s?

@HerraBRE I've failed to find an adequate replacement to several dozen shell scripts which are running an entire web hosting platform, including one for an aerospace company

@HerraBRE With a disclaimer that I don't represent my employer and I'm not getting paid for this advice:

Don't.

K8s makes sense if you use 3rd party tools to manage, observe, inspect workloads. Also so your developer team has a better approximation of prod without having to understand load balancing or networking.

If you were using k8s already I'd say - go for it with single purpose nodes and a daemonset, otherwise just use whatever you already use for orchestration.

@HerraBRE @rysiek I have enough Kubernetes experience to try and convince you to avoid using it for managing any kind of service. Would that help?

@HerraBRE what kind of services?