Advanced Customizations

Customizing your deployment of Kubeflow

This guide has information about advanced customizations for Kubeflow.

Persistent Disks

Frequently data scientists require a POSIX compliant filesystem. For example, most HDF5 libraries require POSIX and don’t work with an object store like GCS or S3. Also, when working with teams you might want a shared POSIX filesystem to be mounted into your notebook environments so that data scientists can work collaboratively on the same datasets.

You can provision your own NFS shares and create Persistent Volume and Persistent Volume Claim objects and then attach them to your Jupyter notebook server via the disks flag.

Configure Jupyter to use the disks

ks param set jupyter disks ${PVC_CLAIM1},${PVC_CLAIM2}

Deploy the environment

ks apply cloud

Start Jupyter You should see your NFS volumes mounted as /mnt/${DISK_NAME}

In a Jupyter cell you can run


You should see output like the following
Filesystem                                                     1K-blocks    Used  Available Use% Mounted on
overlay                                                         98884832 8336440   90532008   9% /
tmpfs                                                           15444244       0   15444244   0% /dev
tmpfs                                                           15444244       0   15444244   0% /sys/fs/cgroup 1055841280   77824 1002059776   1% /mnt/jlewi-kubeflow-test1 1055841280   77824 1002059776   1% /mnt/jlewi-kubeflow-test2
/dev/sda1                                                       98884832 8336440   90532008   9% /etc/hosts
shm                                                                65536       0      65536   0% /dev/shm
tmpfs                                                           15444244       0   15444244   0% /sys/firmware
  • Here jlewi-kubeflow-test1 and jlewi-kubeflow-test2 are the names of the PVCs.
Last modified 28.04.2019: Resolved typos (#665) (44f20b50)