diff --git a/docs/advanced/longhorn-v2.md b/docs/advanced/longhorn-v2.md index 4115dd241f..b6f909c392 100644 --- a/docs/advanced/longhorn-v2.md +++ b/docs/advanced/longhorn-v2.md @@ -12,7 +12,7 @@ Description: How to enable and use the Longhorn V2 Data Engine The Longhorn V2 Data Engine harnesses the power of the Storage Performance Development Kit (SPDK) to significantly reduce I/O latency while boosting IOPS and throughput. The result is a high-performance storage solution that is capable of meeting diverse workload demands. -:::note +:::info important The Longhorn V2 Data Engine is an **Experimental** feature in Harvester v1.4.0 and should not be utilized in a production environment. @@ -28,6 +28,8 @@ Every node with an active Longhorn V2 Data Engine requires the following dedicat ## Limitations +:::info important + The Longhorn V2 Data Engine currently does not support the following operations: - Backing image creation and usage @@ -36,6 +38,8 @@ The Longhorn V2 Data Engine currently does not support the following operations: - Volume encryption - Volume expansion +::: + Within the Harvester context, volumes backed by the Longhorn V2 Data Engine must be added to virtual machines as extra disks. The boot disk of each virtual machine must still be added from an image that is backed by the Longhorn V1 Data Engine. Harvester is unable to live-migrate virtual machines with V2 volumes attached, which means those virtual machines will be shut down during Harvester cluster upgrades. Moreover, snapshots of V2 volumes cannot be created because snapshot and restoration functionality in Harvester relies on volume cloning.