| Field | Type | Description | Value(s) |
|---|---|---|---|
name | string | Volume group name. Must be 1-63 chars: ASCII letters, digits, hyphens, underscores. | |
provisioning | ProvisioningSpec | The provisioning describes how the Physical Volumes are provisioned. |
provisioning
ProvisioningSpec describes how the Physical Volumes are provisioned.| Field | Type | Description | Value(s) |
|---|---|---|---|
volumeSelector | LVMVolumeSelectorSpec | Matches disks to initialize as physical volumes. |
volumeSelector
LVMVolumeSelectorSpec matches disks with CEL.| Field | Type | Description | Value(s) |
|---|---|---|---|
match | Expression | CEL expression matching a disk or partition to use as a physical volume. The expression is evaluated against each discovered volume with the volume variable (the discovered volume) and, for whole disks, thedisk variable. Partitions (e.g. raw volumes) can be matched by theirpartition label via volume.partition_label.A volume declared in the machine config also matches on volume_id,the volume name prefixed by its kind ( u- user, r- raw, s- swap),as in volume_id == "r-lvmdata". A device Talos does not manage as avolume has an empty volume_id.Use volume_id for a whole-disk volume, which carries no partitionlabel to match on. Use it for an encrypted volume too: Talos creates the physical volume on the opened device, never on the ciphertext. Talos matches a declared volume only after the volume manager has prepared it. Provisioning therefore waits for an encrypted volume to be unlocked rather than write to the still-locked device. |