======================
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.
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