Storage considerations

Dynamic storage must be supported on the cluster. The deployment script on a private OpenShift Container Platform (OCP) cluster needs a storage class name that the installer can use.

Before you begin

The supported storage providers for a demo deployment of Cloud Pak for Business Automation include the IBM Storage Suite for IBM Cloud Paks. For more information, see IBM Documentation and Why IBM Storage Suite for IBM Cloud Paks. The following storage options are the most suited from the IBM Storage Suite.

Red Hat OpenShift Container Storage (OCS)
File storage from IBM Spectrum Scale

Before you start the demo environment setup, you must make sure that you have dynamic storage provisioning for the cluster. For more information, see Dynamic provisioning.

Note: Demo deployments do not support the Portworx storage solution.

The deployment script asks for a storage class name that is associated with the dynamic storage you plan to use. Your dynamic storage must have sufficient space for the deployment. For more information, see Storage Classes.

About this task

The administrator must make a note of the storage class to use, and provide this name to the user who runs the deployment script.

Network File System (NFS) storage or some other shareable storage such as Gluster File System (GlusterFS) is needed if you choose not to use the native OCP storage provisioner. You can use the NFS-Client Provisioner along with an NFS share to meet the dynamic storage requirements.

Tip: For more information about the Kubernetes NFS-Client Provisioner, see Kubernetes NFS-Client Provisioner. Follow the instructions to configure NFS server and client for the OCP nodes if you need to set up an NFS server.

You can also go to the following technote to find step-by-step instructions on How do I create a storage class for NFS dynamic storage provisioning in an OpenShift environment?