ReadWriteMany Persistent Volumes#

The following microservices create persistent volume claims (PVCs) that can be mounted on multiple pods and nodes in read-write mode through storage classes in Kubernetes. This access mode is called ReadWriteMany (RWX) in Kubernetes clusters.

NeMo Data Store
NeMo Operator
NeMo Customizer

NIMs can also scale, upgrade and deploy more smoothly with an RWX persistent volume (PV).

The NeMo microservices don’t manage storage classes on your behalf. You must install an appropriate storage provisioner, identified by a StorageClass, before installing their Helm charts.

Select a Storage Class#

Confirm the StorageClass exists in your Kubernetes cluster.
```
kubectl get storageclass
```
In the values.yaml file, set the storageClass key in the persistence dictionary object to NFS-backed StorageClass and accessModes to ReadWriteMany as shown in the following sample.
```
persistence:
  enabled: true
  storageClass: "nfs"
  claimName: datastore-shared-storage
  size: 10Gi
  accessModes:
    - ReadWriteMany
```

Persistent Volume Options#

We recommend that you use a ReadWriteMany-capable filesystem for these cases, such as NFS or CephFS, where the volume can be mounted across different nodes and pods in a read/write access mode.

If you use a CSI, the most common type of storage provisioner, you can see options in this table of Kubernetes CSI Drivers. If you choose a file system from this table, it must be listed as Read/Write Multiple in the Supported Access Modes column, and the Description column should match your environment.

AWS

Review general guidance on using EFS and FSx from AWS.

AWS Peristent Volumes

Oracle

Review general guidance on using OCI File Storage service from Oracle.

Oracle Persistent Volumes