Skip to main content

Concepts

Workspaces come with temporary storage that disappears when stopped. To keep your data, you must use a persistent volume.
Volume typeDescriptionBest forMount pathStorage type
Workspace volumeDedicated, high-performance (NVMe) persistent volume for a single workspaceCode, virtualenvs (pip/conda), per-workspace data/root ($HOME) - fixedCluster volume (PVC-backed, cluster-specific)
Shared volumeTeam-shared POSIX-compatible filesystem backed by S3 object storageDatasets, checkpoints, large artifacts to share across the team/shared (recommended)Object volume (S3-backed, accessible across clusters)
Temporary volumeDefault ephemeral storage included in every workspaceFast scratch space (data is wiped when stopped)VariesEphemeral (emptyDir)
Storage types explained:
  • Object volumes (shared volumes): Backed by S3 object storage, accessible from any cluster in your organization. Behave like network file shares with RWX (read-write-many) semantics across workspaces.
  • Cluster volumes (workspace volumes): Backed by cluster-specific storage (NVMe/PVC), available only within a specific cluster. Behave like dedicated disks with RWO (read-write-once) semantics for a single workspace.

Terminology mapping

ConceptOur termKubernetes (typical)Other productsNotes
Shared (team)Shared volumePV/PVC on NFS/SMB/EFS (RWX)Shared volume (provider-specific); some use commit/reload semanticsNetwork file share, multi-workspace
Per-workspaceWorkspace volumePV/PVC (RWO)Provider volume attached per workload (for example, pod/function)Dedicated disk-like, single workspace
EphemeralTemporary volumeemptyDirLocal workspace/container filesystemDeleted on stop/terminate

Typical workflows

  • Create and Manage: Create a shared volume to store your data.
  • Share: Share datasets and models across workspaces using shared volumes.
  • Persist: Keep per-workspace state in workspace volumes.