Quick (hopefully) question, I'm looking to deploy longhorn on 2 specific nodes on a 10 worker-node cluster. I came across https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/#create-a-storageclass-that-select-a-specific-set-of-nodes But one thing seemed a bit confusing/concerning:

Result: workloads that use Longhorn volumes can run on any nodes. Longhorn only schedules replicas of

my-longhorn-volv-pvc

on the node

node-1

,

node-2

, and

node-3

would that mean that potentially (in my case), workloads would only have a 20% chance of getting scheduled on a node for which longhorn is running (and by extension, where the PVs are)? 1. am I reading this right? 2. does this kb still apply given links in it go to v1.2.2 docs?

1. I think it means when deploy a pod and pvc, then the Longhorn volume related workloads will only launched on the nodes which are labeled. In your case, it will always create workloads, e.g., replicas on this two nodes. 2. Yes, the document is still workable with using the latest version:

1.4.1

and the document is https://longhorn.io/docs/1.4.1/advanced-resources/deploy/node-selector/ 3. As mentioned in the official document, the best practice to deploy Longhorn in a 3 nodes environment. https://longhorn.io/docs/1.4.1/best-practices/#minimum-recommended-hardware

Yeah, we're actually going to be setting the replicas to 1 because we dont actually need replication. We're basically looking for a more dynamic alternative to https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner without all the pitfalls of some of the other dynamic provisioners that cant enforce pvc/pv quotas

maybe longhorn strict-local disk could match your requirement (still longhorn managed, but local replica access ? ) https://longhorn.io/docs/1.4.1/high-availability/data-locality/#data-locality-settings