From e9754a0a8d5208df5e7f8d65312df6f1f17f486f Mon Sep 17 00:00:00 2001
From: Krzysztof Opasiak <k.opasiak@samsung.com>
Date: Thu, 16 Jul 2020 21:06:39 +0200
Subject: [COMMON] Use readinessCheck template inside certInitializer

Instead of manually creating readiness init container let's use our
dedicated template for this.

Issue-ID: OOM-2511
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Idb112e864b7899e7a1e76d139c6cc6a94851a090
---
 kubernetes/common/certInitializer/values.yaml | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

(limited to 'kubernetes/common/certInitializer/values.yaml')

diff --git a/kubernetes/common/certInitializer/values.yaml b/kubernetes/common/certInitializer/values.yaml
index fdee4c9bd2..416282f72a 100644
--- a/kubernetes/common/certInitializer/values.yaml
+++ b/kubernetes/common/certInitializer/values.yaml
@@ -13,8 +13,6 @@
 # limitations under the License.
 
 global:
-  readinessRepository: oomk8s
-  readinessImage: readiness-check:2.0.2
   repository: nexus3.onap.org:10001
   aafAgentImage: onap/aaf/aaf_agent:2.1.20
   aafEnabled: true
@@ -29,6 +27,12 @@ secrets:
     password: '{{ .Values.aafDeployPass }}'
     passwordPolicy: required
 
+readinessCheck:
+  wait_for:
+    - aaf-locate
+    - aaf-cm
+    - aaf-service
+
 aafDeployFqi: "changeme"
 fqdn: ""
 app_ns: "org.osaaf.aaf"
-- 
cgit 1.2.3-korg