From c0ef45b834b02aea5a42cb43987beae6d35c67f6 Mon Sep 17 00:00:00 2001 From: egernug Date: Wed, 18 Nov 2020 13:07:26 +0000 Subject: [PATCH] Update SDNC documentation for NETCONF/TLS certificate management Issue-ID: SDNC-1124 Signed-off-by: egernug Change-Id: Ia0b22ef5c9715e701303e762b1d54ffdf91f5e32 (cherry picked from commit 4537e7e6e555676d687c30557473b5df4d5c2f77 [formerly aecc4a75fac6d92e103db6d6651ac3b13c8fbb4c]) Former-commit-id: 5e4a472df4519bccca128011cea39a496981ed24 --- docs/cert_installation.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/cert_installation.rst b/docs/cert_installation.rst index 221d5fea..44dfe053 100644 --- a/docs/cert_installation.rst +++ b/docs/cert_installation.rst @@ -172,6 +172,8 @@ Confirmation of this functionality can be performed in OOM using the Contrib pro Firstly, CertService will need to be deployed. This will require the global flag *global.cmpv2Enabled* to be set to true in *kubernetes/onap/resources/overrides/aaf-cert-service-environment.yaml* +There is also an additional module that will need to be deployed named platform. This is required for secret creation. + To deploy the EJBCA server the global flag *global.addTestingComponents* in *kubernetes/onap/values.yaml* will need to be set to true. This flag will load the test configuration from *kubernetes/aaf/charts/aaf-cert-service/resources/test/cmpServers.json* -- 2.16.6