When users install Cloud Pak for Data Version 2.5, they may receive
the following message:
“[INFO] [2020-05-13 07:24:31-0757] No storage class
provided, default to static provisioning.”
But a user may want to use dynamic provisioning and have decided
to use a specific storage provisioner for his Cloud Pak for Data. In this case,
it is Network File System (NFS) storage. To achieve this goal, he just needs to
set up the NFS storage properly in the context of Red Hat OpenShift environment
to allow Cloud Pak for Data to utilize it.
Here is the document discussing supported storage providers,
including NFS:
Storage considerations
https://www.ibm.com/support/knowledgecenter/SSQNUZ_2.5.0/cpd/plan/storage_considerations.html
As mentioned in the above document, Kubernetes NFS-Client
Provisioner is needed in the OpenShift V3.11 environment. But before you deploy
the NFS-Client, you must have an existing NFS server that is already configured
outside of the OpenShift cluster. If you are new to OpenShift or NFS-Client-Provisioner,
here is a helpful third-party article on this topic:
“Openshift dynamic NFS persistent volume using NFS-client-provisioner”
https://medium.com/faun/openshift-dynamic-nfs-persistent-volume-using-nfs-client-provisioner-fcbb8c9344e
The Storage Class need to be configured by your OpenShift
administrator before you install IBM Cloud Pak for Data. Here is the document
on how to enable Default StorageClass behavior for an OpenShift V3.11 cluster:
Scenario 2: How to enable Default StorageClass behavior for
a Cluster
https://docs.openshift.com/container-platform/3.11/install_config/storage_examples/storage_classes_dynamic_provisioning.html#example2
#CloudPakforData#CloudPakforDataGroup#Support#SupportMigration