[OOM] Use cert-initializer truststore instead of hard-coded ONAP Root CA 76/123876/7
authorAbdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
Sat, 4 Sep 2021 09:08:36 +0000 (11:08 +0200)
committerAbdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
Thu, 16 Sep 2021 21:43:40 +0000 (23:43 +0200)
commit822eb097fc30cd687de96a1fe78b2dab24332e39
treec5e1b5939b087420bf926dbb82a1c24bac5634b7
parent3980a8cbeb63c885b123ac50033e32ed996bb39a
[OOM] Use cert-initializer truststore instead of hard-coded ONAP Root CA

By adding the certInitializer directives in cds blueprint processor
deployment, we get access to the AAF ONAP Root CA, instead of static file.

Issue-ID: CCSDK-3356
Signed-off-by: Abdelmuhaimen Seaudi <abdelmuhaimen.seaudi@orange.com>
Change-Id: Ifc3d1797905868b268cbfd06237866bf8dc3d3f5
kubernetes/cds/components/cds-blueprints-processor/requirements.yaml
kubernetes/cds/components/cds-blueprints-processor/templates/deployment.yaml
kubernetes/cds/components/cds-blueprints-processor/values.yaml
kubernetes/cds/components/cds-command-executor/values.yaml
kubernetes/cds/components/cds-py-executor/values.yaml
kubernetes/cds/components/cds-sdc-listener/values.yaml
kubernetes/cds/components/cds-ui/values.yaml