[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
diff --git a/kubernetes/so/components/so-bpmn-infra/values.yaml b/kubernetes/so/components/so-bpmn-infra/values.yaml
index 09ad911..9a811d7 100755
--- a/kubernetes/so/components/so-bpmn-infra/values.yaml
+++ b/kubernetes/so/components/so-bpmn-infra/values.yaml
@@ -34,7 +34,8 @@
readinessCheck:
wait_for:
- - so-mariadb-config
+ jobs:
+ - '{{ include "common.release" . }}-so-mariadb-config-job'
#################################################################
# Secrets metaconfig