Elaborate on hostdefiner docs

Author: shlomitn

docs/content/configuration/configuring_hostdefiner.md

@@ -5,20 +5,29 @@
 
 Some of the parameters within the HostDefiner custom resource are configurable. Use this information to help decide whether the parameters for your storage system need to be updated.
 
-Starting from 1.13.0 the configuation parameters are saved in the config map ibm-csi-hostdefiner-config and remain persistent on CSI software upgrade. The config map should be created in the same namespace as the pod.
-Applying configuration changes still requires host definer restart.
+Starting from 1.13.0 the configuation parameters are saved in the config map ibm-csi-hostdefiner-config and remain persistent on CSI software upgrade.
+
+The old way, of adding the parameters in the hostdefiner yaml is obsolete!{: important}
+
+The config map should be created in the same namespace as the pod.
+For the configuration changes to take effect, the host definer must be restarted (by deleting the hostdefiner pod).
 
 Because the configuration is saved in a config map - it can be defined even before the upgrade to 1.13.0
 
 Use standard configmap CLIs to update the configuration, examples below.
 All CLIs accept an optional -n parameter to specify the namepsace
 
-Create/update a configuration parameter (replace key value with actual parameter setting):
+Create configmap in order to update a configuration parameter (replace "key" and "value" with actual parameter setting):
 ```
   kubectl create configmap ibm-csi-hostdefiner-config --from-literal=key=value
 ```
 The key may be any key from the below table, under Field. The possible values are also specified in the table.
 
+More than one value can be specified, as needed. For example:
+```
+  kubectl create configmap ibm-csi-hostdefiner-config --from-literal=connectivityType=fc --from-literal=portSet=portset64
+```
+
 Get a ConfigMap
 ```
   kubectl get configmap ibm-csi-hostdefiner-config
@@ -31,7 +40,7 @@ Delete a ConfigMap:
 
 Delete a ConfigMap entry:
 
-There's no simple command to delete an entry. You can either use:
+In order to remove an entry or update the configmap, one can either use:
 ```
   kubectl edit configmap ibm-csi-hostdefiner-config
 ```

docs/content/installation/install_hostdefiner_github.md

@@ -1,7 +1,13 @@
+
+{{site.data.keyword.attribute-definition-list}}
+
 # Installing the host definer with GitHub
 
 The host definer for IBM® block storage CSI driver can be installed directly with GitHub.
 
+Before installing or upgrading, if one wants non-default configuration settings, a configmap must be created See [Configuring the host definer](../configuration/configuring_hostdefiner.md). The old way of setting parameters in yaml is obsolete.{: important}
+
+
 Use the following steps to install the HostDefiner custom resource, with [GitHub](https://github.com/IBM/ibm-block-csi-operator).
 
 1. Download the custom resource manifest from [GitHub](https://github.com/IBM/ibm-block-csi-operator).

docs/content/installation/install_hostdefiner_openshift_web.md

@@ -1,11 +1,15 @@
+
+{{site.data.keyword.attribute-definition-list}}
+
 # Installing the host definer with the OpenShift web console
 
 When using the Red Hat® OpenShift® Container Platform, the HostDefiner custom resource can be installed directly from OpenShift Container Platform web console, through the OperatorHub. 
 
+Before installing or upgrading, if one wants non-default configuration settings, a configmap must be created See [Configuring the host definer](../configuration/configuring_hostdefiner.md). The old way of setting parameters in yaml is obsolete.
+{: .important}
+
 1. From the web console, navigate to the **IBM block storage CSI driver operator** within your project namespace.
 
 2. From the IBM block storage CSI Host Definer driver tab, click Create `HostDefiner`.
 
-    A YAML file opens in the web console. This file can be left as-is, or edited as needed. For more information, see [Configuring the host definer](../configuration/configuring_hostdefiner.md).
-
 3. After everything is created, wait until the **Status** is _Running_.

docs/content/installation/install_hostdefiner_operatorhub.md

@@ -3,6 +3,10 @@
 
 # Installing the host definer with OperatorHub.io
 
+Before installing or upgrading, if one wants non-default configuration settings, a configmap must be created See [Configuring the host definer](../configuration/configuring_hostdefiner.md). The old way of setting parameters in yaml is obsolete.
+{: .important}
+
+
 When using OperatorHub.io, the host definer can be installed directly from the OperatorHub.io website.
 
 From [IBM block storage CSI driver operator](https://operatorhub.io/operator/ibm-block-csi-operator-community) on OperatorHub.io, apply the HostDefiner custom resource definition yaml provided. For more information, see [Configuring the host definer](../configuration/configuring_hostdefiner.md).

docs/content/release_notes/whats_new.md

@@ -1,3 +1,6 @@
+
+{{site.data.keyword.attribute-definition-list}}
+
 # What's new in 1.13.0
 
 IBM® block storage CSI driver 1.13.0 adds support for:
@@ -14,8 +17,4 @@ For information about the resolved issues in version 1.13.0, see [1.13.0](change
 If you have any configuration changes that you want saved over upgrade, notice the following.{: attention}
 
 For configuration persistancy over upgrade, a config map procedure was added:
-Prior to upgrading to IBM® block storage CSI driver 1.13.0 (or above) from releases before 1.13.0, please create a configmap with your existing changes, for example:
-`kubectl create configmap ibm-csi-hostdefiner-config --from-literal=portSet=portset64`
-If you have more than one configuration change, you can add more `--from-literal=key=value` at the end of the above line. This configuration will be saved over upgrade.
-
-More info regarding this configmap in [Configuring the host definer](../configuration/configuring_hostdefiner.md)
+Prior to upgrading to IBM® block storage CSI driver 1.13.0 (or above) from releases before 1.13.0, please create a configmap with your existing changes. Please refer to [Configuring the host definer](../configuration/configuring_hostdefiner.md)

docs/content/using/using_hostdefinition_labels.md

@@ -10,6 +10,12 @@ Please refer to the host definer configuration page for more information.
 
 Adding labels to nodes allows for greater control over the system nodes, when using dynamic host definition.
 
+## Setting node to be managed by hostdefiner
+To set a node to be managed by hostdefiner, meaning that hosts will be created for this node, label the node with `hostdefiner.block.csi.ibm.com/manage-node=true`
+```
+  kubectl label node <node-name1> <node-name2> hostdefiner.block.csi.ibm.com/manage-node=true
+```
+
 ## Blocking a specific node definition from being deleted
 
 To block a specific host definition from being deleted by the host definer, you can add the following label to the node: `hostdefiner.block.csi.ibm.com/avoid-deletion=true`.