I’m trying to see if LINSTOR is a good fit for my use case. I’m using clusterapi to generate k8s clusters on the fly. For this I set up an Incus cluster on my nodes using LINSTOR as storage provider. This works great but now I want to use the same LINSTOR cluster (with a different storage pool) to use as persistent volumes inside those k8s clusters.
So I have the clusterapi Incus provider which creates VMs on the cluster and create the k8s clusters, however the LINSTOR CSI provider requires each VM to also be a satellite node.
Should I install the satellite package on each VM and add them to the cluster or is this a bad idea?
Thanks for the response, do you mean that each cluster should install it’s own piraeus operator? Does this mean that each cluster will deploy it’s own LINSTOR cluster or can I chose to only deploy a satellite and reuse the linstor cluster I use for the Incus cluster?
I am simply advising you use the Operator because you will require more than just the linstor-satellite packages. You will also require the LINSTOR CSI driver, and possibly the node affinity controller, or some other bits I am forgetting,. All of which we package and deploy within the Operator. It’s usually easiest to deploy everything the k8s native way via containers and DaemonSets which will automatically scale and install as nodes are added, etc, than manually having to install a package on the OS.
However, It sounds like you already have an existing LINSTOR cluster though, and that the k8s nodes will not have any local storage themselves. Everything will just be served remotely via DRBD disklessly from a separate core set of storage nodes. While I have not done this myself, I believe this article may explain exactly what you need: Integrating External LINSTOR Clusters With Kubernetes by Using the LINSTOR CSI Driver - LINBIT