fixing invalid portal db images 01/42101/2
authorMandeep Khinda <mandeep.khinda@amdocs.com>
Wed, 11 Apr 2018 01:35:54 +0000 (21:35 -0400)
committerMandeep Khinda <mandeep.khinda@amdocs.com>
Wed, 11 Apr 2018 21:37:05 +0000 (21:37 +0000)
commit06ad9b7ab0cdecb9af73cbf7e2ac9684039b536d
tree773dcf4b42c5db62c2fb169e595bfee814f70ebf
parentf39bd633c0acea07c3502a984178afa65f6c2b52
fixing invalid portal db images

Finding strange issues with image pulling and names subst.
When using registry.hub.docker.com and an Always pull policy
the Job pod would sit there pulling images forever even though
they are actually up to date and present.
Therefore reverting back to plain old oomk8s/blah

Issue-ID: OOM-746

Change-Id: Iec5de0e1314ac85fa4e8de6599922f1e0fd0e367
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
kubernetes/portal/charts/portal-mariadb/templates/job.yaml
kubernetes/portal/charts/portal-mariadb/values.yaml