LVMLogicalVolume

Scope: Cluster
Version: v1alpha1

The LVMLogicalVolume resource defines the storage where a PV will be created in.

  • spec
    object

    Required value

    • spec.actualLVNameOnTheNode
      string

      Required value

      Actual LV name on the node.

      Pattern: ^[a-z0-9]([a-z0-9-.]{0,251}[a-z0-9])?$

    • spec.lvmVolumeGroupName
      string

      Required value

      LVMVolumeGroup resource’s name which VG will be used for LV creation.

      Pattern: ^[a-z0-9]([a-z0-9-.]{0,251}[a-z0-9])?$

    • spec.size
      integer or string

      Required value

      The desired LV size. Might be specified as number or percent size of total VG or thin pool space (for thin pool total space is counted by actual thin pool size multiply by allocationLimit value).

      Note, that if you specify the percent size, the LV will be automatically extended when VG, thin pool or thin pool’s allocationLimit value is extended.

      Pattern: ^[0-9]+(\.[0-9]+)?(E|P|T|G|M|k|Ei|Pi|Ti|Gi|Mi|Ki)?$|^[1-9][0-9]?%$|100%

      Minimal length: 1

    • spec.source
      object

      Source of the volume, if present.

      • spec.source.kind
        string

        Required value

        Kind of the source. Kind LVMLogicalVolume means that current resource is clone. Kind LVMLogicalVolumeSnapshot means that current resource is a restored volume.

        Allowed values: LVMLogicalVolume, LVMLogicalVolumeSnapshot

      • spec.source.name
        string

        Required value

        The name of the resource current resource is created from.

    • spec.thick
      object
      • spec.thick.contiguous
        boolean

        If true, the Logical Volume will be created with the contiguous flag. Use it carefully as LV might not be created even if there is enough space in VG.

      • spec.thick.volumeCleanup
        string

        The method of the volume cleanup before deletion. If the parameter is not set, after deleting the PV, the data may be deleted or it may remain. There is no guarantee of deletion or non-deletion:

        • RandomFillSinglePass — the volume will be overwritten with random data once before deletion. This option is not recommended for solid-state drives, as it reduces the lifespan of the drive.
        • RandomFillThreePass — the volume will be overwritten with random data three times before deletion. This option is also not recommended for solid-state drives, as it reduces the lifespan of the drive.
        • Discard — all blocks of the volume will be marked as free using the discard` system call before deletion. This option is only applicable to solid-state drives.

        Allowed values: RandomFillThreePass, RandomFillSinglePass, Discard

    • spec.thin
      object

      Specifies used ThinPool. Needs only if LV has thin type.

      • spec.thin.poolName
        string

        Required value

        Used thin pool name.

        Pattern: ^.*$

    • spec.type
      string

      Required value

      LV type.

      Allowed values: Thick, Thin