This example shows you how to deploy the NFS Server Provisioner on an OpenShift
cluster where the Rook Ceph storage system is used.
As an example, you can deploy the NFS Server Provisioner using the Helm chart provided here .
For the nfs storage class, set “allowVolumeExpansion=true”
For the underlying persistent volume, specify a size of 1 TiB.
On the block storage system class, rook-ceph-block in this case, set
allowVolumeExpansion=true
Download two YAML files here: nfs-server-provisioner.yml and
nfs-scc.yml .
note
If your read-write-once block pv storage class is not rook-ceph-block, then
replace rook-ceph-block with your preferred read-write-once block pv storage
class in the nfs-server-provisioner.yaml file below.
note
In this example, the size of the underlying persistent volume is specified as 1 TiB. You are
recommended to increase the size by 1 TiB for each additional ML workspace that
will be created. For example, increase the size by 5 TiB for 5 ML
workspaces.
note
The yaml file below has a line that will download the nfs server image from
quay.io/kubernetes_incubator/nfs-provisioner:v2.3.0 . If your installation is
airgapped, download the file to a local repository and change the path
accordingly.
Install Path 1: Installing using the oc command and yaml files:
If you do not have Tillerless Helm v2 set up, then you can simply apply
the nfs-server-provisioner.yaml file as follows: $
oc create -f nfs-server-provisioner.yaml -n cml-nfs
Install Path 2: Installing using the oc command and Tillerless Helm v2:
$ oc delete scc nfs-scc
$ oc delete clusterrole cml-nfs-nfs-server-provisioner
$ oc delete clusterrolebinding cml-nfs-nfs-server-provisioner
$ oc delete namespace cml-nfs
$ helm tiller run cml-nfs -- helm delete cml-nfs --purge
$ oc delete scc nfs-scc securitycontextconstraints.security.openshift.io "nfs-scc" deleted
