The module lifecycle stage: General Availability

Available with limitations in:  CE

Available without limitations in:  SE, SE+, EE

The module is designed to manage local block storage based on LVM. It enables creating StorageClasses in Kubernetes using the LocalStorageClass resource.

Creating StorageClass for the local.csi.storage.deckhouse.io CSI driver by users is prohibited.

Available access modes for the module: RWO.

To work with volume snapshots, the snapshot-controller module must be connected. The ability to work with volume snapshots is available only in commercial editions of Deckhouse Kubernetes Platform and only when using LVM-thin volumes.

How the module works

The sds-local-volume module uses local disks of cluster nodes to create block storage based on LVM.

The module supports two operation modes: LVM (Thick) and LVM-thin. For more details on the differences between modes, see the FAQ.

When to use the module

The sds-local-volume module is suitable for the following scenarios:

  • Maximum storage performance comparable to local disk performance is required (LVM (Thick) mode).
  • Applications need fast access to data on local node disks without network latency.
  • Disk space needs to be used efficiently through on-demand volume allocation (LVM-thin mode).

The module is not suitable for scenarios that require:

  • Network storage with the ability to migrate volumes between nodes.
  • Data replication between nodes.

System requirements and recommendations

The module has the following system requirements and recommendations:

  • It is recommended to use standard Linux kernels included in supported distributions.
  • It is not recommended to use other SDS (Software Defined Storage) solutions to provide SDS disks for Deckhouse Kubernetes Platform.

Additional materials

  • Quick start — example of module setup for creating Thick storage on three cluster nodes.
  • Configuration — description of module configuration parameters.
  • Custom Resources — description of custom resources used by the module.
  • Usage — volume cleanup, data migration between PVCs, and volume snapshots.
  • FAQ — answers to frequently asked questions about the module.