helm -n onap upgrade dev-dcaegen2-services --reuse-values --values new-config.yaml oom/kubernetes/dcaegen2-services\r
\r
Where the contents of ``new-config.yaml`` file is:\r
- .. code-block:: bash\r
+ .. code-block:: yaml\r
\r
dcae-ves-collector:\r
applicationConfig:\r
\r
After the upgrade, the new auth method value should be visible inside dev-dcae-ves-collector-application-config-configmap Config-Map.\r
It can be verified by running:\r
+\r
.. code-block:: bash\r
\r
kubectl -n onap get cm <config map name> -o yaml\r
\r
For VES Collector:\r
+\r
.. code-block:: bash\r
\r
kubectl -n onap get cm dev-dcae-ves-collector-application-config-configmap -o yaml\r
---------------------------------------------------------------\r
In order to utilize the externalRepo openAPI schema files defined in `OOM <https://gerrit.onap.org/r/gitweb?p=oom.git;a=tree;f=kubernetes/dcaegen2-services/resources/external>`_ repository and installed with dcaegen2 module, follow below steps.\r
\r
-.. note:: \r
+.. note::\r
For more information on generating schema files, see `External-schema-repo-generator (OOM Utils repository) <https://gerrit.onap.org/r/gitweb?p=oom/utils.git;a=tree;f=external-schema-repo-generator>`_\r
- \r
+\r
Default ONAP deployment for Istanbul release makes available the SA88-Rel16 OpenAPI schema files; optionally SA99-Rel16 files can be loaded using the `Generator script <https://gerrit.onap.org/r/gitweb?p=oom/utils.git;a=blob;f=external-schema-repo-generator/generator/generate.sh>`_ based on the steps documented in `README <https://git.onap.org/oom/utils/tree/external-schema-repo-generator/README.md>`_\r
\r
\r
optional: true\r
- name: 'dev-dcae-external-repo-configmap-sa88-rel16'\r
type: configmap\r
- mountPath: /opt/app/VESCollector/etc/externalRepo/3gpp/rep/sa5/MnS/blob/SA88-Rel16/OpenAPI \r
+ mountPath: /opt/app/VESCollector/etc/externalRepo/3gpp/rep/sa5/MnS/blob/SA88-Rel16/OpenAPI\r
optional: true\r
\r
If more than a single external schema is required add new config map to object 'externalVolumes' like in above example. Make sure that all external schemas (all openAPI files) are reflected in the schema-map file.\r
\r
In order to use the X.509 certificates obtained from the CMP v2 server (so called "operator`s certificates"), refer to the following description:\r
\r
-:ref:`Enabling TLS with external x.509 certificates <external-tls-helm>`\r
+:ref:`Enabling TLS with external x.509 certificates <tls_enablement>`\r
\r
Example values for VES Collector:\r
- .. code-block:: bash\r
+ .. code-block:: yaml\r
\r
global:\r
cmpv2Enabled: true\r
name: ves-cmpv2-keystore-password\r
key: password\r
create: true\r
-\r