Setting up dynamic provisioning

Before you begin

About this task

The steps in this procedure use the Kubernetes NFS-Client Provisioner (from the Kubernetes SIGs organization) to set up dynamic provisioning with NFS storage.

Your NFS server must be accessible from your Red Hat OpenShift Container Platform cluster.

Mirroring the provisioner images to a private container registry

Configuring dynamic storage

To configure dynamic storage:

1. Run the cpd-cli manage login-to-ocp command to log in to the cluster as a user with sufficient permissions to complete this task. For example:

   cpd-cli manage login-to-ocp \
   --username=${OCP_USERNAME} \
   --password=${OCP_PASSWORD} \
   --server=${OCP_URL}

   Tip: The login-to-ocp command takes the same input as the oc login command. Run oc login --help for details.
2. If you mirrored the images to a private container registry, update the global image pull secret so that the cluster can access the Kubernetes NFS-Client Provisioner images.

   The global image pull secret must contain the credentials of an account that can pull images from the private container registry:

   cpd-cli manage add-cred-to-global-pull-secret \
   --registry=${PRIVATE_REGISTRY_LOCATION} \
   --registry_pull_user=${PRIVATE_REGISTRY_PULL_USER} \
   --registry_pull_password=${PRIVATE_REGISTRY_PULL_PASSWORD}

3. Set the following environment variables:
   1. Set NFS_SERVER_LOCATION to the IP address or fully qualified domain name (FQDN) of the NFS server:

      export NFS_SERVER_LOCATION=<server-address>

   2. Set NFS_PATH to the exported path where you want the provisioner to create sub-directories. (The default path is /.)

      export NFS_PATH=<path>

   3. Set PROJECT_NFS_PROVISIONER to the project (namespace) where you want to deploy the Kubernetes NFS-Client Provisioner provisioner. The recommended project is nfs-provisioner; however you can specify any project.
      Important: You must specify an existing project (namespace).

      export PROJECT_NFS_PROVISIONER=<project-name>

   4. Set NFS_STORAGE_CLASS to the name that you want to use for the NFS storage class:

      export NFS_STORAGE_CLASS=<storage-class-name>

      By default, the documentation uses managed-nfs-storage, but you can pick a different storage class name.

   5. Set the NFS_IMAGE to the correct value for your Red Hat OpenShift Container Platform architecture:

      Architecture	Command
      x86-64	export NFS_IMAGE=k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2
      ppc64le	export NFS_IMAGE=gcr.io/k8s-staging-sig-storage/nfs-subdir-external-provisioner:v4.0.2
      s390x	export NFS_IMAGE=gcr.io/k8s-staging-sig-storage/nfs-subdir-external-provisioner:v4.0.2

4. Run the following command to set up dynamic provisioning:

   cpd-cli manage setup-nfs-provisioner \
   --nfs_server=${NFS_SERVER_LOCATION} \
   --nfs_path=${NFS_PATH} \
   --nfs_provisioner_ns=${PROJECT_NFS_PROVISIONER} \
   --nfs_storageclass_name=${NFS_STORAGE_CLASS} \
   --nfs_provisioner_image=${NFS_IMAGE}

   If the command succeeds, the storage class is ready to use.

5. Add the mountOptions entry to the storage class.
   Important: The nfsvers=3 option is required for the following services:

   • Db2
   • Db2 Warehouse
   • Watson Knowledge Catalog
   • OpenPages
   • Big SQL
   • Watson Query

   However, the option is highly recommended for all environments.

   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