[SO] Check for job instead of container for so-mariadb-config 18/123418/5
authorPrabhjot Singh Sethi <prabhjot@aarnanetworks.com>
Fri, 20 Aug 2021 17:10:23 +0000 (22:40 +0530)
committerKrzysztof Opasiak <k.opasiak@samsung.com>
Fri, 27 Aug 2021 14:25:47 +0000 (14:25 +0000)
commit46e1756c3beefa0108e847b02225de381d9a6c7c
tree8041fe5711d097096fa246903cf66ebecaa21fdf
parentcb6c366d0bfdf65c7397994f59f230be83fcac9b
[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
kubernetes/so/components/so-bpmn-infra/values.yaml
kubernetes/so/components/so-catalog-db-adapter/values.yaml
kubernetes/so/components/so-etsi-sol005-adapter/values.yaml
kubernetes/so/components/so-nssmf-adapter/values.yaml
kubernetes/so/components/so-openstack-adapter/values.yaml
kubernetes/so/components/so-request-db-adapter/values.yaml
kubernetes/so/components/so-sdc-controller/values.yaml
kubernetes/so/values.yaml