Figure 2-5 Setting up NFS server primer -1 3. Install the Helm chart through IBM Cloud Private. Click the  nfs-client tile as in Figure 2-5   and configure the Helm chart with the following values for your cluster. We documented  the figures as follows: – You see callout letters beside each field where you enter a value. – Each callout letter maps to a description in these steps.  – At the end of each description  the default value is displayed in parentheses (). – Bolded values are variables that you might have to change.  – You can apply the unbolded values in your environment if you follow the configuration  that is described here. Values for callout letters a to c apply to Figure 2-6 on page 31. Table 2-1 Values for callout letters a to c a. Helm release name  is the name for the helm release. Make sure that each helm release in the cluster  has a unique name. Otherwise  you get an error  and you must redeploy the release to a different  name. (nfsc) b. Target Namespace  is the namespace where the helm release resources will be deployed. This chart  requires the  kube-system  namespace if callout letter  j    Run as system-cluster-critical  is selected.  [This is the recommended option. It gives the provisioner priority over the pods that rely on it.]  (kube-system) c. Target Cluster  is the cluster that you are targeting with the deployment. (local-cluster). 30  Implementation Guide for IBM Blockchain Platform for Multicloud