Storage Tags
The storage tag feature enables only certain nodes or disks to be used for storing Longhorn volume data. For example, performance-sensitive data can use only the high-performance disks which can be tagged as fast
, ssd
or nvme
, or only the high-performance node tagged as baremetal
.
This feature supports both disks and nodes.
The tags can be set up using the Longhorn UI:
+New Node Tag
or +New Disk Tag
to add new tags.All the existing scheduled replica on the node or disk won’t be affected by the new tags.
When multiple tags are specified for a volume, the disk and the node (the disk belong to) must have all the specified tags to become usable.
When creating a volume, specify the disk tag and node tag in the UI.
Use Kubernetes StorageClass parameters to specify tags.
You can specify tags in the default Longhorn StorageClass by adding parameter nodeSelector: "storage,fast"
in the ConfigMap named longhorn-storageclass
.
For example:
apiVersion: v1
kind: ConfigMap
data:
storageclass.yaml: |
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: longhorn
annotations:
storageclass.kubernetes.io/is-default-class: "true"
provisioner: driver.longhorn.io
allowVolumeExpansion: true
reclaimPolicy: "Delete"
volumeBindingMode: Immediate
parameters:
numberOfReplicas: "3"
staleReplicaTimeout: "480"
diskSelector: "ssd"
nodeSelector: "storage,fast"
If Longhorn is installed via Helm, you can achieve that by editing persistence.defaultNodeSelector
in values.yaml.
Alternatively, a custom storageClass setting can be used, e.g.:
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: longhorn-fast
provisioner: driver.longhorn.io
parameters:
numberOfReplicas: "3"
staleReplicaTimeout: "480" # 8 hours in minutes
diskSelector: "ssd"
nodeSelector: "storage,fast"
© 2019-2024 Longhorn Authors | Documentation Distributed under CC-BY-4.0
© 2024 The Linux Foundation. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.