Add helm v3 usage instructions in build and install guide

Change-Id: I1f02ac57ee4d35683595ffeec0aab7446d2fb914
Issue-ID: INT-1893
Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>

diff --git a/docs/BuildGuide.rst b/docs/BuildGuide.rst
index 9856b7b..e47dd80 100644 (file)
--- a/docs/BuildGuide.rst
+++ b/docs/BuildGuide.rst
@@ -106,6 +106,8 @@ For the list of all available options check script usage info.
 
 .. note:: Skip this step if you have already all necessary resources and continue with **Part 3. Populate local nexus**
 
+.. note:: Docker images collector supports both helm v2 and v3. Please note that helm v3 support was added in Guilin release of OOM and as of Honolulu release helm v2 will be obsolete.
+
 Create repository containing OS packages to be installed on all nodes:
 
 ::

diff --git a/docs/InstallGuide.rst b/docs/InstallGuide.rst
index 30451f2..6c0ec76 100644 (file)
--- a/docs/InstallGuide.rst
+++ b/docs/InstallGuide.rst
@@ -307,6 +307,14 @@ Second one controls time zone setting on host. It's value should be time zone na
 
 ``'timesync.servers'``, ``'timesync.slewclock'`` and ``'timesync.timezone'`` settings can be used independently.
 
+In the Guilin release, OOM added support for `Helm`_ v3 Kubernetes package manager. Offline installer leverages on the v2 version by default. Should you desire to deploy Onap with helm v3 you need to set following variable:
+
+::
+
+    helm_version: v3.x.x
+
+The exact version string to use above should be picked from ``'build/data_lists/infra_bin_utils.list'`` file.
+
 Final configuration can resemble the following::
 
     resources_dir: /data
@@ -538,3 +546,4 @@ Usage is basically the same as with the default chroot way - the only difference
 .. _OOM ONAP: https://docs.onap.org/projects/onap-oom/en/latest/index.html
 .. _Offline installer: https://gerrit.onap.org/r/q/oom/offline-installer
 .. _RKE: https://rancher.com/products/rke/
+.. _Helm: https://helm.sh/