aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/common/certInitializer/values.yaml
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2021-04-19 16:00:49 +0200
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2021-05-06 06:29:46 +0000
commitbd94a04227a235319b3246e52cadc7c1e96f9c22 (patch)
treef4f817dd18994012f85d9bceb1685c409e8d1f2f /kubernetes/common/certInitializer/values.yaml
parentf6465e1e1386cd090ab9a125683304e57f373c19 (diff)
[COMMON][CERTS] Allow to provide custom certs easily
Instead of mandating to provide custom certificates before creation of helm packages, let's propose to include certificates from a known secret or configmap. The current implementation will first search for secret and if not provided will look for configmap. Issue-ID: OOM-2731 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: If2f90adc18efe59c0516db9409964a236bd17a66
Diffstat (limited to 'kubernetes/common/certInitializer/values.yaml')
-rw-r--r--kubernetes/common/certInitializer/values.yaml10
1 files changed, 9 insertions, 1 deletions
diff --git a/kubernetes/common/certInitializer/values.yaml b/kubernetes/common/certInitializer/values.yaml
index 52b2765329..74a2b37568 100644
--- a/kubernetes/common/certInitializer/values.yaml
+++ b/kubernetes/common/certInitializer/values.yaml
@@ -15,6 +15,15 @@
global:
aafAgentImage: onap/aaf/aaf_agent:2.1.20
aafEnabled: true
+ # Give the name of a config map where certInitializer will onboard all certs
+ # given (certs must be in pem format)
+ customCertsConfigMap:
+ # Give the name of a secret where certInitializer will onboard all certs given
+ # (certs must be in pem format)
+ # this one superseedes previous one (so if both are given, only certs from
+ # secret will be onboarded).
+ customCertsSecret:
+
pullPolicy: Always
@@ -37,7 +46,6 @@ readinessCheck:
- aaf-cm
- aaf-service
-aafDeployFqi: "changeme"
fqdn: ""
app_ns: "org.osaaf.aaf"
fqi: ""