Increase portal-db initial liveness probe time

The initial liveness probe against portal-db was
too quick, causing the container to be terminated
in the middle of DB schema initialization and
leaving the DB in a corrupted state.  This change
increases the initial delay before the liveness
probe.

Change-Id: I2f428ea33b60c3a99ca1e49dc8e59405aa4d824c
Issue-ID: PORTAL-283
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>

diff --git a/kubernetes/portal/charts/portal-mariadb/values.yaml b/kubernetes/portal/charts/portal-mariadb/values.yaml
index ab46984..ae5849e 100644 (file)
--- a/kubernetes/portal/charts/portal-mariadb/values.yaml
+++ b/kubernetes/portal/charts/portal-mariadb/values.yaml
@@ -77,14 +77,14 @@ affinity: {}
 
 # probe configuration parameters
 liveness:
-  initialDelaySeconds: 10
+  initialDelaySeconds: 300
   periodSeconds: 10
   # necessary to disable liveness probe when setting breakpoints
   # in debugger so K8s doesn't restart unresponsive container
   enabled: true
 
 readiness:
-  initialDelaySeconds: 10
+  initialDelaySeconds: 300
   periodSeconds: 10
 
 ## Persist data to a persitent volume