there are currently 3 types of storage:
nfs: shared file system
File volumes behave like docker host mounts and are fully managed for you including redundancy and backups. They can be accessed by multiple pods simultaneously and support concurrent read/writes to some degree. This is useful for configs and other shared data that doesn't have high performance requirements. Since the intent is to emulate docker volume behavior, this is the default choice if you don't know which volume type you need.
lv2: local nvme
LV2 is exposed as block storage to the vm. Usually it will be automatically formated and mounted as ext4 but can also be used as raw block device available in /dev/volumes/ by not specifying any volumeMounts. Note that directly attached storage is not highly available. In case of a host failure there's a manual recovery process involved that will be executed whenever the host is back. users of lv2 should prepare for that scenario.
creating your first volume
docker supports volumes natively, and the cli works out of the box
k8s uses PersistentVolumeClaim to create volumes
docker supports volumes natively, and the compose spec works out of the box
volumes can be accessed via webdav via https://files.kraudcloud.com or davs://files.kraudcloud.com depending on your client.
You will find username/password in your profile under "Files Login".