Note:  If you deviate from the recommended path and install the helm release for nfs-client in  a namespace other than  kube-system , follow these conventions: GLYPH<SM590000> Assign a name for the namespace is a value  other than  kube-system .  use -n < namespace_name >  where < namespace_name > is a value  other than  kube-system , as in this example  statement: use -n default  GLYPH<SM590000> Double check that  Run as system-cluster-critical  was unchecked when you deployed  the helm release. In the current version of IBM Cloud Private, that setting works with the  kube-system  namespace only. i. Run the following command to check the pods and deployment of the  nfs-full-provisioner. Typical output for the command is also shown: ii. Run the following command to check that the test pod has “Completed”  successfully. Typical output for the command is also shown: iii. Run the following command to view the newly created StorageClass and confirm  that it has been made the default. Typical output for the command is also shown: kubectl get sc kubectl get pod,deploy -l app=nfs-full NAME READY STATUS RESTARTS AGE pod/nfsf-nfs-full-7bdff6d5f6-w9ld9 1/1 Running 0 2m43s NAME READY UP-TO-DATE AVAILABLE AGE deployment.extensions/nfsf-nfs-full 1/1 1 1 2m44s kubectl get pod,deploy -l app=test-nfs-full NAME READY STATUS RESTARTS AGE pod/test-pod-nfsf-nfs-full 0/1 Completed 0 3m18s NAME PROVISIONER AGE fully-managed-nfs-storage (default) nfs.io/nfs-full-provisioner 3m25s glusterfs kubernetes.io/glusterfs 2d6h image-manager-storage kubernetes.io/no-provisioner 65d logging-storage-datanode kubernetes.io/no-provisioner 65d mongodb-storage kubernetes.io/no-provisioner 65d 2.3.2 Gluster File System (GlusterFS) GlusterFS is an open source clustered file storage solution (scale-out network attached  storage file system) designed by Gluster, Inc. now formerly RedHat (since its acquisition in  2011). Instead of having code directly in the kernel like NFS, GlusterFS is a File System in  User Space (FUSE). In FUSE, the file system code runs in user space and makes calls to the  FUSE module, which connects it to the kernel interfaces.  GlusterFS uses Heketi, which is the RESTful management interface that manages your  GlusterFS volumes. Heketi enables the administrator to check the state of its gluster file  system with a number of commands. The commands can show everything from the overall  topology of the scale-out network to the state of the current cluster, nodes, and devices. Kubernetes has a GlusterFS provisioner plug-in that is built in that creates GlusterFS  persistent volumes in response to persistent VolumeClaims for storage. There are many  42  Implementation Guide for IBM Blockchain Platform for Multicloud