Creation

Volume creation happens on demand for ephemeral volumes. In contrast Persistent volumes need to be created explicitly via the CLI, web UI, or API prior to first use starting with V4.

Your cluster administrator configures storage provisioners that determine the storage backend and access policies for your organization. Your workflow creates and/or uses one or more storage volumes which are directories or resources managed by a provisioner.

Volume Naming Rules

A volume name must follow these rules:

Length: Between 1 and 255 characters
No path separators: Cannot contain / or \
No path traversal: Cannot be . and cannot contain ..
No null bytes: Cannot contain a null byte (\0)

Any other characters — letters in any case, digits, spaces, dots, underscores, hyphens, and other punctuation — are allowed.

Valid examples:

my-dataset
Research_Data-2024
project 1
results.v2

Invalid examples:

my/dataset          # Contains a path separator
data\set            # Contains a path separator
..                  # Path traversal
my..dataset         # Contains path traversal (..)

These rules prevent volume names from escaping the storage boundary. The same rules are enforced by the CLI, web UI, and API.

Validation Errors

If you encounter a validation error when creating a volume, check that your volume name:

Is not empty and is no longer than 255 characters
Does not contain a path separator (/ or \)
Is not . and does not contain ..
Does not contain a null byte