From e9de7f65855420db72a5c585b224c0b0b31a9a47 Mon Sep 17 00:00:00 2001 From: Sylvain Desbureaux Date: Wed, 14 Oct 2020 09:07:14 +0200 Subject: [CLAMP] Give times to mariadb to come up On some environments, clamp database is restarted in the middle of the init script. The consequence is then a weird behavior, especially if the users are not set. This patch adds more time to the DB in the environment override file (which is supposed to be used in slow environnement). Issue-ID: OOM-2597 Signed-off-by: Sylvain Desbureaux Change-Id: Ieb700afbb27610dbad18d860b7fb85ac95c2bb0d --- kubernetes/clamp/components/clamp-mariadb/values.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'kubernetes/clamp') diff --git a/kubernetes/clamp/components/clamp-mariadb/values.yaml b/kubernetes/clamp/components/clamp-mariadb/values.yaml index 492145ae07..f9a31b6b86 100644 --- a/kubernetes/clamp/components/clamp-mariadb/values.yaml +++ b/kubernetes/clamp/components/clamp-mariadb/values.yaml @@ -55,15 +55,17 @@ affinity: {} # probe configuration parameters liveness: - initialDelaySeconds: 10 + initialDelaySeconds: 30 periodSeconds: 10 + timeoutSeconds: 3 # necessary to disable liveness probe when setting breakpoints # in debugger so K8s doesn't restart unresponsive container enabled: true readiness: - initialDelaySeconds: 10 + initialDelaySeconds: 30 periodSeconds: 10 + timeoutSeconds: 3 ## Persist data to a persitent volume persistence: -- cgit 1.2.3-korg