[HV-VES-KAFKA] Add doc updates for hv-ves kafka
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
Change-Id: I3b377f39fd2b0b764f88990b6a8b97fa63ed158d
Issue-ID: DCAEGEN2-3083
diff --git a/docs/sections/services/ves-hv/run-time-configuration.rst b/docs/sections/services/ves-hv/run-time-configuration.rst
index c2352c7..830ed66 100644
--- a/docs/sections/services/ves-hv/run-time-configuration.rst
+++ b/docs/sections/services/ves-hv/run-time-configuration.rst
@@ -7,7 +7,13 @@
======================
HV-VES dynamic configuration is primarily meant to provide DMaaP Connection Objects (see :ref:`dmaap-connection-objects`).
-These objects contain information necessary to route received VES Events to correct Kafka topic. This metadata will be later referred to as Routing definition.
+
+.. note:: Kafka config info.
+ In the case of HV-VES, this configuration method is purely used as a generic reference.
+ The underlying kafka connection config is managed as part of the dcea helm configuration.
+
+These objects contain information necessary to route received VES Events to correct Kafka topic.
+This metadata will be later referred to as Routing definition.
Collector uses DCAE-SDK internally, to fetch configuration from Config Binding Service.
@@ -45,4 +51,4 @@
The configuration is created from HV-VES Cloudify blueprint by specifying **application_config** node during ONAP OOM/Kubernetes deployment. Example of the node specification:
.. literalinclude:: resources/blueprint-snippet.yaml
- :language: yaml
\ No newline at end of file
+ :language: yaml