summaryrefslogtreecommitdiffstats
path: root/kubernetes/portal/charts/portal-mariadb/templates/job.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-05-22[PORTAL] Move portal subcharts to componentsKrzysztof Opasiak1-91/+0
In order to allow to define dependencies per subchart let's move all of them to components and make sure that they can be build independently. Issue-ID: AAF-1134 Change-Id: Ia75ba66d9338dbacaea500c20f6a5b384d1685a1 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
2020-04-20[Portal] Move (unused) readinessImage to globalSylvain Desbureaux1-1/+1
All helm charts in ONAP are setting readinessImage to global part (it can then be easy to bump version for everybody at once). Portal Job is not using it and use a local version. Move to use global one for consistency Issue-ID: OOM-2373 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I5400ab595773ffc7111bc43f64c48b7c9a4c2dcd
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak1-2/+2
ONAP is too big to be deployed using helm install so we need to use a custom helm plugin helm deploy. This script deloys onap component by component instead of deploying evrything at once. Unfortunately this script also modifies the helm release by appending component name to it. As a result of this behavior our objects are called for example: onap-mariadb-galera-mariadb-galera-0 instead of just being called onap-mariadb-galera-0. This patch simplifies this naming convention by replacing all direct usages of .Release.Name with common.release macro which strips the component specific part from the release name. Issue-ID: OOM-2275 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
2018-08-30Apache2 License additiontoshrajbhardwaj1-0/+1
Issue-ID: OOM-1306 Change-Id: I1a617718006ee845d675fead74ce075c3390ac2f Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
2018-04-24Make all services independent of helm Release.NameBorislavG1-3/+3
Issue-ID: OOM-906 Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-04-11fixing invalid portal db imagesMandeep Khinda1-3/+3
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>
2018-04-06Correcting portal k8s configmap service namesMandeep Khinda1-2/+2
The service.name is really a port name and was being used wrong. Need a better way than this to get dependant chart names. This gets it working. Issue-ID: OOM-842 Change-Id: I6a78a5adb0e69524a90aa3386009a0d87ebed73c Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-05Removing portal schema from configmapMandeep Khinda1-0/+90
-Trying a new way to initialize maria db's. -Docker image contains project sources and sql files are fetched and executed agains't the target database. -duplicates are silently ignored. -A script that takes some basic params will do the heavy lifting -A 2nd job to make some OOM specific changes (carry over from amsterdam) -docker image has been pushed to oomk8s under the 2.0.0 number Issue-ID: OOM-858 Change-Id: I56d0c9c5aa1d3c4a9df2998634b9147db626d1fb Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>