From feac15e0badc9af769044051c4368788d8a7bcca Mon Sep 17 00:00:00 2001 From: Gary Wu Date: Tue, 15 May 2018 14:57:36 -0700 Subject: 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 --- kubernetes/portal/charts/portal-mariadb/values.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kubernetes/portal/charts/portal-mariadb/values.yaml b/kubernetes/portal/charts/portal-mariadb/values.yaml index ab469848f2..ae5849eb27 100644 --- 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 -- cgit 1.2.3-korg