summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authordfarrelly <david.farrelly@est.tech>2019-04-10 19:08:47 +0000
committerdfarrelly <david.farrelly@est.tech>2019-04-10 19:08:47 +0000
commitdd0365a7af08b6731d616eb223e49ab41a513bed (patch)
treeffe53566a098e699e16dc4d227d9c99041c08247 /docs
parentd1a63a6b35566d81b7282d4c2e08cb6a1f3857db (diff)
Add current SAN listing to TLS support
Issue-ID: DCAEGEN2-1414 Change-Id: Iddc2d36a697ee8d946e2c3ee55fd369c56c95e9a Signed-off-by: dfarrelly <david.farrelly@est.tech>
Diffstat (limited to 'docs')
-rw-r--r--docs/sections/tls_enablement.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/sections/tls_enablement.rst b/docs/sections/tls_enablement.rst
index 2d7b0071..5d4925c6 100644
--- a/docs/sections/tls_enablement.rst
+++ b/docs/sections/tls_enablement.rst
@@ -10,6 +10,10 @@ Solution overview
-----------------
1. Certificate generation:
This step is done manually currently using Test AAF instance in POD25. Required namespace, DCAE identity (dcae@dcae.onap.org), roles and Subject Alternative Names for all components are preset. Using the procedure desribed by AAF (using ``agent.sh``), the certificates are generated. Using the Java keystore file (``.jks``) generated from AAF, create the .pem files and load them into tls-init-container under dcaegen2/deployment repository. The image has a script that runs when the image is deployed. The script copies the certificate artifacts into a Kubernetes volume. The container is used as an "init-container" included in the Kubernetes pod for a component that needs to use TLS.
+
+ Current SAN listing::
+
+ bbs-event-processor, bbs-event-processor.onap, bbs-event-processor.onap.svc.cluster.local, config-binding-service, config-binding-service.onap, config-binding-service.onap.svc.cluster.local, dcae-cloudify-manager, dcae-cloudify-manager.onap, dcae-cloudify-manager.onap.svc.cluster.local, dcae-datafile-collector, dcae-datafile-collector.onap, dcae-datafile-collector.onap.svc.cluster.local, dcae-hv-ves-collector, dcae-hv-ves-collector.onap, dcae-hv-ves-collector.onap.svc.cluster.local, dcae-pm-mapper, dcae-pm-mapper.onap, dcae-pm-mapper.onap.svc.cluster.local, dcae-prh, dcae-prh.onap, dcae-prh.onap.svc.cluster.local, dcae-tca-analytics, dcae-tca-analytics.onap, dcae-tca-analytics.onap.svc.cluster.local, dcae-ves-collector, dcae-ves-collector.onap, dcae-ves-collector.onap.svc.cluster.local, deployment-handler, deployment-handler.onap, deployment-handler.onap.svc.cluster.local, holmes-engine-mgmt, holmes-engine-mgmt.onap, holmes-engine-mgmt.onap.svc.cluster.local, holmes-rule-mgmt, holmes-rules-mgmt.onap, holmes-rules-mgmt.onap.svc.cluster.local, inventory, inventory.onap, inventory.onap.svc.cluster.local, policy-handler, policy-handler.onap, policy-handler.onap.svc.cluster.local
2. Plugin and Blueprint:
Update blueprint to include new (optional) node property (tls_info) to the type definitions for the Kubernetes component types. The property is a dictionary with two elements: