Skip to content

Commit 5450d3c

Browse files
committed
Update readme
1 parent 0a4f1af commit 5450d3c

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

charts/longhorn/README.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
### How does LH decide which node's disk to use as storage
44

5-
There are 3 ways https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/
5+
There are 3 ways (could be combined together) https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/
66
* storag tag feature https://longhorn.io/docs/1.8.1/nodes-and-volumes/nodes/storage-tags/
77
* node selectors that will restrict LH to certain nodes only (and disks on these nodes)
88
* using https://longhorn.io/docs/archives/1.2.2/references/settings/#create-default-disk-on-labeled-nodes
@@ -12,3 +12,8 @@ There are 3 ways https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/
1212
Use 2 articles below to get detailed information
1313
* https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/
1414
* https://longhorn.io/docs/1.8.1/nodes-and-volumes/nodes/default-disk-and-node-config/
15+
16+
### Running LH on subset of Nodes (via nodeSelectors) has a limitation
17+
18+
The workloads that use PV (from LH) can only run on the nodes where LH runs. Check the Result description in the article below:
19+
* https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/#deploy-longhorn-components-only-on-a-specific-set-of-nodes

0 commit comments

Comments
 (0)