This message was deleted.
# longhorn-storagea
adamant-kite-43734
04/27/2023, 6:44 PMThis message was deleted.
n
narrow-egg-98197
04/29/2023, 9:02 AM1. 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👍 1
s
stale-egg-64993
05/01/2023, 2:53 PMYeah, 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
stale-egg-64993
05/01/2023, 2:53 PMbit outside the typical use case for longhorn, but lacking better options
a
alert-policeman-61846
06/01/2023, 5:35 PMmaybe 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
alert-policeman-61846
06/01/2023, 5:37 PM@narrow-egg-98197 wrt to node selector, still unclear for me. In my context, all my nodes have longhorn components. However i want to define a storageclass targeting only certain nodes to host the related replicas.
alert-policeman-61846
06/01/2023, 5:40 PMI guess https://longhorn.io/docs/1.4.1/volumes-and-nodes/storage-tags/#kubernetes is close to my solution.
Using Nodes and Disks labels.
The documentation only mentions longhorn ui usage. Is it possible to apply the labels on longhorn CR with kubectl apply (on Node ?)
240 Views