[backport 1.6]: Fix encrypted Longhorn PVC size to meet LUKS2 minimum requirement (!7598) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR updates the encrypted Longhorn PVC size from 1Mi to 20Mi.

The 1Mi size was introduced in MR !4420 (merged). However, encrypted Longhorn volumes use LUKS2, which requires a minimum volume size greater than 16MiB due to the default LUKS2 header size.

Because the requested size was below this requirement, the volume creation was rejected by the Longhorn admission webhook and the PVC remained in Pending state.

$ kubectl get pvc encrypted-longhorn-pvc-test -n longhorn-system
NAME                          STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS                     VOLUMEATTRIBUTESCLASS   AGE
encrypted-longhorn-pvc-test   Pending                                      longhorn-encryption-per-volume   <unset>                 20m

Warning  ProvisioningFailed  failed to provision volume with StorageClass "longhorn-encryption-per-volume":
rpc error: code = Internal desc = Bad response statusCode [500].
message=failed to create volume: unable to create volume pvc-xxxx:
admission webhook "validator.longhorn.io" denied the request:
invalid volume size 10485760, need to be bigger than 16MiB,
default LUKS2 header size for encryption

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Apr 27, 2026 by Dragos Gerea

[backport 1.6]: Fix encrypted Longhorn PVC size to meet LUKS2 minimum requirement

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports