summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/ves-hv/installation-helm.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/sections/services/ves-hv/installation-helm.rst')
-rw-r--r--docs/sections/services/ves-hv/installation-helm.rst13
1 files changed, 8 insertions, 5 deletions
diff --git a/docs/sections/services/ves-hv/installation-helm.rst b/docs/sections/services/ves-hv/installation-helm.rst
index b9bf6da9..87aca24b 100644
--- a/docs/sections/services/ves-hv/installation-helm.rst
+++ b/docs/sections/services/ves-hv/installation-helm.rst
@@ -4,7 +4,7 @@
HV-VES Helm Installation
========================
-Starting from ONAP/Honolulu release, HV-VES is installed with a DCAEGEN2-Services Helm charts.
+Starting from ONAP/Honolulu release, HV-VES is installed with a DCAEGEN2-Services Helm charts.
HV-VES application is configured by default to use TLS/SSL encryption on TCP connection.
Disable TLS security - Helm based deployment
@@ -22,7 +22,7 @@ For example:
helm -n onap upgrade dev-dcaegen2-services --reuse-values --values new-config.yaml oom/kubernetes/dcaegen2-services
Where the contents of ``new-config.yaml`` file is:
- .. code-block:: bash
+ .. code-block:: yaml
dcae-hv-ves-collector:
applicationConfig:
@@ -35,17 +35,20 @@ For small changes like this, it is also possible to inline the new value:
After the upgrade, the security.sslDisable property should be changed and visible inside dev-dcae-ves-collector-application-config-configmap Config-Map.
It can be verified by running:
+
.. code-block:: bash
kubectl -n onap get cm <config map name> -o yaml
For HV-VES Collector:
+
.. code-block:: bash
kubectl -n onap get cm dev-dcae-hv-ves-collector-application-config-configmap -o yaml
For apply new configuration by HV-VES Collector the application restart might be necessary. It could be done by HV-VES helm reinstallation:
+
.. code-block:: bash
helm -n onap upgrade dev-dcaegen2-services --reuse-values --set dcae-hv-ves-collector.enabled="false" oom/kubernetes/dcaegen2-services
@@ -57,10 +60,11 @@ Using external TLS certificates obtained using CMP v2 protocol
In order to use the X.509 certificates obtained from the CMP v2 server (so called "operator`s certificates"), refer to the following description:
-:ref:`Enabling TLS with external x.509 certificates <external-tls-helm>`
+:ref:`Enabling TLS with external x.509 certificates <tls_enablement>`
Example values for HV-VES Collector:
- .. code-block:: bash
+
+ .. code-block:: yaml
global:
cmpv2Enabled: true
@@ -80,4 +84,3 @@ Example values for HV-VES Collector:
name: hv-ves-cmpv2-keystore-password
key: password
create: true
-