When not in use, Domino project files are stored and versioned in the Domino blob store. When a Domino execution is started from a project, the projects files are copied to a Kubernetes persistent volume that is attached to the compute node and mounted in the run.
When a user starts a new job, Domino brokers assignment of a new execution pod to the cluster. This pod will has an associated Persistent Volume Claim (PVC) which defines for Kubernetes what type of storage it requires.
If an idle PV exists matches the PVC, Kubernetes mounts that PV on the node it assigns to host the pod, and the job or workspace starts. If an appropriate idle PV does not exist, Kubernetes creates a new PV according to the Storage Class.
When the user completes their job or workspace, the PV data is written to the Domino File System, and the PV unmounts and sits idle until it is either reused for the user’s next job or garbage collected. By reusing PVs, users who are actively working in a project do not have to repeatedly copy data from the blob store to a PV.
A job only matches with a fresh PV or one previously used by that project. PVs are not reused between projects.