summaryrefslogtreecommitdiffstats
path: root/kubernetes/vid/templates/job.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-02-15[VID] Don't hardcode mariadb-galera passwordKrzysztof Opasiak1-5/+3
Let's use common secret template to generate user credentials for VID DB and depend on mariadb-galera to generate secure enough root password. Issue-ID: OOM-2293 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ib474e202e9e35e6b2959d29648f542a89c87a4e5
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
2019-11-18[VID] Use mariadb galera common chartSylvain Desbureaux1-9/+8
Instead of using "own" galera chart, reuse chart placed in common part of OOM installation. Will ease move to common galera cluster (which is not done by this commit). Change-Id: I843c89ed4899055e9502268089d0e01f28fe37ae Issue-ID: VID-704 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2018-12-21global image pull issuedkamdocs1-1/+1
Issue-ID: OOM-1563 Change-Id: I383dbec29291ba5b13d613f60d8eb343b9c59dda Signed-off-by: dkamdocs <devesh.kumar@amdocs.com>
2018-10-23Consistent naming for vid deploymentJulien Barbot1-0/+83
Change-Id: I7ae002ae214f1c0ca858a96c79e2b74f15d13405 Issue-ID: OOM-729 Signed-off-by: Julien Barbot <julien@barbot.org>