EPHEMERAL volume grows before user volume is provisioned on system disk

[nitrocb]

Hello together,

I am currently trying to set up a user volume on the system disk. This is my configuration:

apiVersion: v1alpha1
kind: VolumeConfig
name: EPHEMERAL
provisioning:
    diskSelector:
        match: system_disk
    minSize: 2GiB
    grow: true
---
apiVersion: v1alpha1
kind: UserVolumeConfig
name: local-storage
provisioning:
  diskSelector:
    match: system_disk
  minSize: 10GB
  maxSize: 10GB

The idea is, that the user volume takes exactly 10GB space on the system disk, while the EPHEMERAL volume should take the rest.
But it seems that all volumeConfigs are processed before the UserVolumeConfigs and the effect is, that the EPHEMERAL volume takes all the remaining space on the system disk and leaves no space for the user volume.

Is it really intended like this? If I set the size for the EPHEMERAL volume to a certain amount, then this is working fine.
But I want to use all remaining space for it.

Thanks in advance!

[smira]

System volumes are provisioned before any user volumes to guarantee that they don't fail the allocation.

Within the same class though, volumes which are set to grow: true are provisioned last to ensure that the allocation doesn't fail.

Talos provides many ways to set the maxSize so that EPHEMERAL doesn't occupy the whole disk.

[nitrocb]

Ok, this means that my only solutions to use up all my disk space in my situation are:

• configure maxSize precisely for every partition
• use grow: true for my user volume and maxSize for EPHEMERAL

Is that correct?

[smira]

It depends on your layout, number of disks, and desired volume sizes.

The important bit is that system volumes are provisioned before user volumes.

[nitrocb]

Thanks @smira for the clarification