Hello All ,
We have already done a recent setup for IBM Cloudpak for data , one of the notes we found in the docs which needs a fix i guess is Setting up dynamic provisioning
the below step in the docs i guess need to be switched to
`oc patch storageclass ${NFS_STORAGE_CLASS} --type='json' -p='[{"op": "replace", "path": "/mountOptions", "value": ["nfsvers=3", "nolock"]}]'`
the reason is that If a StorageClass
already exists with the same name, the oc apply
command will not work to just update the mountOptions
because apply
attempts to manage the entire resource definition, and conflicts might occur with existing configurations not specified in the below current definition.
so instead of the below for , my experience is to run the above command
Run the following command to update the storage class:
cat <<EOF |oc apply -f -
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ${NFS_STORAGE_CLASS}
provisioner: nfs-client-provisioner
parameters:
archiveOnDelete: "false"
mountOptions:
- nfsvers=3
- nolock
EOF
Ibm |
remove preview |
|
Setting up dynamic provisioning |
NFS does not support dynamic storage provisioning by default, and Red Hat OpenShift does not include a provisioner plug-in to create an NFS storage class. Therefore, you must set up dynamic storage provisioning on your NFS server. |
View this on Ibm > |
|
|
------------------------------
Mohamed Issa
------------------------------