[Feature Request]: Using control planes and nodes together. i.e. make every control plane also an agent with Longhorn about terraform-hcloud-kube-hetzner HOT 7 CLOSED

Additional questions for the pros: I've been reading up on Longhorn and everyone says that C*X11 servers are too small in combination with Longhorn. I can understand if volumes are being synced between servers, but is this still an issue if everything is stored on Hetzner Volumes?

If this is still an issue, is there a way to still use Hetzner Volumes in a different way? All I am trying to do is create a cluster with as few resources as possible for now until I have to scale further and where backups are not required (ie: where data is stored somewhere outside of the servers)

from terraform-hcloud-kube-hetzner.

Why do you use Longhorn on top of Hetzner volumes? Just use hcloud-volumes for RWO and if you need RWX use openebs-nfs-provisioner with hcloud-volumes as backend.

from terraform-hcloud-kube-hetzner.

@aleksasiriski I thought that that was a requirement? Based on this line:

In the case of using Longhorn, you can use Hetzner volumes instead of using the node's own storage by specifying a value from 10 to 10000 (in GB)

The way I read it is 'if you want to use Hetzner Volumes, enable Longhorn', but it seems that my assumption is wrong?

In that situation, if I disable Longhorn then my Hetzner Volumes will keep working?

from terraform-hcloud-kube-hetzner.

@Taronyuu We indeed need to make the text clearer, Hetzner volumes with longhorn is in fact fully optional, by default hcloud csi that is enabled by default will use volumes.

Awesome! Will it break something if I:

1. Set the agent node count to 0
2. Disable longhorn
3. Enable deploying on master planes

I think disabling Longhorn (even when all of my volumes are provisioned on Hetzner Volumes) will be the biggest breaking change, but I am not sure? I already have items provisioned using Hetzner volumes but did not specifically mention Longhorn.

I'll PR soon for an updated documentation to make this more clear :)

from terraform-hcloud-kube-hetzner.

PRs always welcome!

About 1 and 3, of course you have to cordon, drain, kubectl delete node, and normally it should be ok since everything can be scheduled on your control planes with the proper flag.

About 2. I do not know really, it could break. If it's a production setup, best to do blue green like deploy via a new cluster.

from terraform-hcloud-kube-hetzner.

@aleksasiriski @ifeulner Folks, that more down your alley, could you help here please 🙏

from terraform-hcloud-kube-hetzner.

@Taronyuu We indeed need to make the text clearer, Hetzner volumes with longhorn is in fact fully optional, by default hcloud csi that is enabled by default will use volumes.

from terraform-hcloud-kube-hetzner.