aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/so/components/so-bpmn-infra
diff options
context:
space:
mode:
authorPrabhjot Singh Sethi <prabhjot@aarnanetworks.com>2021-08-20 22:40:23 +0530
committerKrzysztof Opasiak <k.opasiak@samsung.com>2021-08-27 14:25:47 +0000
commit46e1756c3beefa0108e847b02225de381d9a6c7c (patch)
tree8041fe5711d097096fa246903cf66ebecaa21fdf /kubernetes/so/components/so-bpmn-infra
parentcb6c366d0bfdf65c7397994f59f230be83fcac9b (diff)
[SO] Check for job instead of container for so-mariadb-config
so-bpmn-infra deployment init container waits on so-mariadb-config pod to complete instead of checking job status itself. This causes issues when the completed config job container finishes and gets cleaned up due to garbage collector, after which so-bpmn-infra pod gets stuck in init state forever. Fixing other instances of waiting for so-mariadb-config job as well. Issue-ID: OOM-2799 Signed-off-by: Prabhjot Singh Sethi <prabhjot@aarnanetworks.com> Change-Id: Ib6d1b53d52c178386a743558c4b45b8f8748487b
Diffstat (limited to 'kubernetes/so/components/so-bpmn-infra')
-rwxr-xr-xkubernetes/so/components/so-bpmn-infra/values.yaml3
1 files changed, 2 insertions, 1 deletions
diff --git a/kubernetes/so/components/so-bpmn-infra/values.yaml b/kubernetes/so/components/so-bpmn-infra/values.yaml
index 09ad91191d..9a811d768d 100755
--- a/kubernetes/so/components/so-bpmn-infra/values.yaml
+++ b/kubernetes/so/components/so-bpmn-infra/values.yaml
@@ -34,7 +34,8 @@ global:
readinessCheck:
wait_for:
- - so-mariadb-config
+ jobs:
+ - '{{ include "common.release" . }}-so-mariadb-config-job'
#################################################################
# Secrets metaconfig