Fixed CHANGELOG

CHANGELOG.md

@@ -29,9 +29,9 @@
   obviates extending the Trident storage class API to support new parameters
   (Issue [#93](https://github.com/NetApp/trident/issues/93)).
 - **Kubernetes:** Added the ability to rename an existing backend.
-- **Kubernetes:** SolidFire defaults to use CHAP if Kubernetes version is
-  >= 1.7 and a `trident` access group doesn't exist. Setting AccessGroup or
-  UseCHAP in config overrides this behavior.
+- **Kubernetes:** SolidFire defaults to use CHAP if Kubernetes version is >= 1.7
+  and a `trident` access group doesn't exist. Setting AccessGroup or UseCHAP in
+  config overrides this behavior.
 - **Docker:** The aggregate attribute in ONTAP config files is now optional.
 
 ## v18.01.0

docs/kubernetes/operations/tasks/backends.rst

@@ -68,3 +68,23 @@ utility, which you may need to install first.
 .. code-block:: bash
 
   tridentctl get backend -o json | jq '[.items[] | {backend: .name, storageClasses: [.storage[].storageClasses]|unique}]'
+
+Updating a backend
+------------------
+
+Once you have a new :ref:`backend configuration <Backend configuration>` file, run:
+
+.. code-block:: bash
+
+  tridentctl update backend <backend-name> -f <backend-file>
+
+If backend update fails, something was wrong with the backend configuration or
+you attempted an invalid update.
+You can view the logs to determine the cause by running:
+
+.. code-block:: bash
+
+  tridentctl logs
+
+Once you identify and correct the problem with the configuration file you can
+simply run the update command again.

trident-installer/sample-input/backend-ontap-nas.json

@@ -1,6 +1,7 @@
 {
     "version": 1,
     "storageDriverName": "ontap-nas",
+    "backendName": "customBackendName",
     "managementLIF": "10.0.0.1",
     "dataLIF": "10.0.0.2",
     "svm": "trident_svm",