Skip to main content

Data Storage Management

The Ephemeral File System (or Container File System) in Puzl is designed for temporary data storage necessary for a pod’s operation. It is automatically created with a pod and erased when the pod terminates. This system is particularly suited for transient data requirements.

  • Ephemeral File System is ideal for storing temporary files and session data, with a size limit of 50 GB per pod's container.
  • Users are billed only for the capacity used, not the entire allocated space. However, it's recommended to use ephemeral fs cautiously for data storage, as its existence is contingent on the pod's lifecycle. Any malfunction in the pod can lead to the loss of data stored in ephemeral fs.

Understanding the distinction between the ephemeral file system and volumes is crucial for effective data management in Puzl. While ephemeral fs is temporary, volumes provide a persistent data storage solution.

  • Utilizing volumes is advisable for storing data that needs to persist beyond the lifespan of a particular pod.
  • Utilizing volumes are required if you want to share some data between multiple running pods.

Volume mounting modes in Kubernetes dictate how volumes can be accessed by pods. Puzl supports two primary modes, catering to different application requirements.

This mode allows a volume to be mounted with read-write access by a single pod at any given time. To mount the volume to another pod, the current one must be deleted.

mode enables a volume to be mounted by multiple pods simultaneously, allowing concurrent read and write operations. This mode is suitable for scenarios requiring shared access to storage across different pods.

Not all storage classes support ReadWriteMany mounting mode. If you need to share your volume between multiple pods, you can use volumes based on sharedfs storage class.

If you create a pod via Puzl dashboard, all volumes will be mounted by the following path: /media/<volume_name>.