[weberc2]

Right, but now you're running Kubernetes for a single server, which is the very definition of overkill. Installing Kubernetes isn't easy, at least not when you consider DNS, ingres/load balancing, logging, etc.

[orange222]

Scenario #1: Installing kubernetes, helm and then installing your app

1. Spend maybe 2-3 full days install kubernetes, helm

2. Spend maybe 3-4 hours installing your app through helm because you're new to installing things in kubernetes.

3. The next app that you want to install on your server is only 20 minutes away, now that you understand how kube and helm work.

Scenario #2:

1. Install app directly on server, hunt down dependencies and other weird things, probably takes 1 day at least, to do the whole installation.

2. The next app that you want to install will take the same amount of time again.

I'd go with Scenario #1 as it is more scalable if I want to install more apps on my server.

[tlrobinson]

Wait, what happened to just using a published Docker image? No need to hunt down dependencies.

I've found using docker-compose is a nice way to do basic orchestration for "self-hosted" type apps.

[berti]

> Install app directly on server, hunt down dependencies and other weird things, probably takes 1 day at least, to do the whole installation.

What distro are you running? Either I am very spoilt with Arch (+AUR) or this is way off the mark.

[snazz]

Really depends on the package. I’ve had programs that take about a day to install, because the source wasn’t really portable and I really needed to get it to build, and I’ve had programs that are just five commands and it runs. It’s more work if you get the source from upstream than if you get it from ports or Portage or the AUR.

[the_duke]

It's still not trivial, but with kubeadm [1] it is much, much easier than it used to be.

[1] https://kubernetes.io/docs/setup/independent/create-cluster-...

[weberc2]

My experience was with kubeadm. If that’s easy mode, I shudder to think of how things were before!