Skip to main content
NetApp Solutions

Define Persistent Volume Claim

Contributors kevin-hoke netapp-asubhas
PDFs

This article demonstrates how to define a persistent volume claim on a Jupyter notebook.

  1. Save the following YAML to a file to create a PVC of type Basic.

    kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: basic
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 100Gi
  storageClassName: netapp-file

  2. Apply the YAML file to your Iguazio Kubernetes cluster.

Kubectl -n default-tenant apply -f <your yaml file>

Attach NetApp Volume to the Jupyter Notebook

Iguazio offers several managed services to provide data scientists with a full end-to-end stack for development and deployment of AI/ML applications. You can read more about these components at the Iguazio Overview of Application Services and Tools.

One of the managed services is Jupyter Notebook. Each developer gets its own deployment of a notebook container with the resources they need for development. To give them access to the NetApp Cloud Volume, you can assign the volume to their container and resource allocation, running user, and environment variable settings for Persistent Volume Claims is presented in the following image.

For an on-premises configuration, on the Trident setup to enable NetApp ONTAP data management capabilities, such as taking Snapshot copies of your data or model for versioning control. Add the following line in your Trident back- end config file to make Snapshot directories visible:

{
    …
    "defaults": {
        "snapshotDir": "true"
    }
}

You must create a Trident back- end config file in JSON format, and then run the following Trident command to reference it:

tridentctl create backend -f <backend-file>

Figure showing input/output dialog or representing written content