Note on ServiceAccount dependency

Change-Id: I2bb2762c15130b692906d3c7d03ac0f20a05cf43
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>
Issue-ID: DCAEGEN2-2918
Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>

2 files changed, 34 insertions, 2 deletions

diff --git a/docs/sections/installation_oom.rst b/docs/sections/installation_oom.rst
index 789e0180..f71675bf 100644
--- a/docs/sections/installation_oom.rst
+++ b/docs/sections/installation_oom.rst
@@ -222,6 +222,36 @@ All DCAE component charts follows standard Helm structure. Each Microservice cha
 
 Using helm, any of DCAE microservice can be deployed/upgraded/uninstalled on-demand.
 
+``Pre-Install``
+
+.. note::
+  This step is only required when helm install should be done on different releasename/prefix from rest of ONAP deployment
+
+With Istanbul release, OOM team included support for ServiceAccount in ONAP deployment to limit the pod access to API server.
+
+Following packages has been added under oom/common to support pre-provisioning of cluster roles and ServiceAccount management
+
+  * `ServiceAccount <https://git.onap.org/oom/tree/kubernetes/common/serviceAccount/values.yaml>`_ 
+  * `RoleWrapper <https://git.onap.org/oom/tree/kubernetes/common/roles-wrapper>`_
+ 
+When deployed, these chart will create the ServiceAccount and Role (based on override) and required Rolebinding (to associate the Serviceaccount to a role).
+
+ONAP deployment by default includes the required provisioning of roles under release name (such as "dev") under which ONAP is deployed. For subsequent
+helm installation under same release name prefix (i.e dev-) no further action is required.
+
+When Helm install is required under different releasename prefix, then execute following command prior to running helm install.
+
+   .. code-block:: bash
+
+        helm install <DEPLOYMENT_PREFIX>-role-wrapper local/roles-wrapper -n <namespace>
+
+
+Followed by install of required service/chart
+
+    .. code-block:: bash
+
+        helm -n <namespace> install <DEPLOYMENT_PREFIX>-dcaegen2-services oom/kubernetes/dcaegen2-services
+
 
 ``Installation``
 
@@ -229,12 +259,14 @@ Review and update local copy of dcaegen2-service ``values.yaml`` oom/kubernetes/
 to ensure component is enabled for deployment (or provide as command line override)
 
     .. code-block:: bash
-        helm -n <namespace> install <DEPLOYMENT_PREFIX>-dcaegen2-services -dcaegen2-services oom/kubernetes/dcaegen2-services
+
+        helm -n <namespace> install <DEPLOYMENT_PREFIX>-dcaegen2-services oom/kubernetes/dcaegen2-services
 
 
 Service component can also be installed individually from oom/kubernetes/dcaegen2-services/components/<dcae-ms-chart>
 
     .. code-block:: bash
+
         helm -n onap install dev-dcaegen2-services-ves-mapper oom/kubernetes/dcaegen2-services/components/dcae-ves-mapper -f values.yaml
 
 Using -f flag override file can be specified which will take precedence over default configuration. 
diff --git a/docs/sections/release-notes.rst b/docs/sections/release-notes.rst
index 9df3ce73..31c32b0e 100644
--- a/docs/sections/release-notes.rst
+++ b/docs/sections/release-notes.rst
@@ -100,7 +100,7 @@ Release Data
 | **Release designation**              | 9.0.0 Istanbul                                         |
 |                                      |                                                        |
 +--------------------------------------+--------------------------------------------------------+
-| **Release date**                     | 2021-10-28                                             |
+| **Release date**                     | 2021-11-18                                             |
 |                                      |                                                        |
 +--------------------------------------+--------------------------------------------------------+