aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/clamp/components/clamp-mariadb
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2020-10-14 09:07:14 +0200
committersebdet <sebastien.determe@intl.att.com>2020-10-14 09:25:30 +0200
commite9de7f65855420db72a5c585b224c0b0b31a9a47 (patch)
tree5f9758463655bb78bf73e6953208379cc6552dad /kubernetes/clamp/components/clamp-mariadb
parentc08c8ffa8ec4f063c22e19acdc0a1e23edd4f26f (diff)
[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 <sylvain.desbureaux@orange.com> Change-Id: Ieb700afbb27610dbad18d860b7fb85ac95c2bb0d
Diffstat (limited to 'kubernetes/clamp/components/clamp-mariadb')
-rw-r--r--kubernetes/clamp/components/clamp-mariadb/values.yaml6
1 files changed, 4 insertions, 2 deletions
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: