From 55bc6b116945dff140ddc1e09ebb3828b079d045 Mon Sep 17 00:00:00 2001 From: BorislavG Date: Wed, 6 Jun 2018 15:36:09 +0000 Subject: Fix SO startup problem SO healthcheck fails due to so db taking long time to initialize. Current solution: increase liveliness and readiness timeouts to 300. Issue-ID: OOM-1127 Change-Id: I18c77d1599769385245de6dceaacfc2c40cdeed3 Signed-off-by: BorislavG --- kubernetes/so/charts/mariadb/values.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kubernetes/so/charts/mariadb/values.yaml b/kubernetes/so/charts/mariadb/values.yaml index 186f825af7..6ea438649b 100644 --- a/kubernetes/so/charts/mariadb/values.yaml +++ b/kubernetes/so/charts/mariadb/values.yaml @@ -46,14 +46,14 @@ affinity: {} # probe configuration parameters liveness: - initialDelaySeconds: 90 + 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: 90 + initialDelaySeconds: 300 periodSeconds: 10 ## Persist data to a persitent volume -- cgit 1.2.3-korg