summaryrefslogtreecommitdiffstats
path: root/kubernetes/multicloud/charts/multicloud-pike/templates
AgeCommit message (Collapse)AuthorFilesLines
2020-09-18[MULTICLOUD] provision multicloud-pike with msb https endpointBin Yang1-0/+4
ONAP MSB component disabled http endpoint during Frankfurt release multicloud-pike component has to utilize MSB https endpoint instead Issue-ID: MULTICLOUD-1195 Signed-off-by: Bin Yang <bin.yang@windriver.com> Change-Id: Ieea57dce0cebe85771d6d19932cd48085da54da0
2020-07-23[MULTICLOUD] Make MULTICLOUD compatible with Kubernetes v1.17kwasiel1-1/+1
Issue-ID: OOM-2459 Signed-off-by: Katarzyna Wasiel <katarzyna.wasiel@nokia.com> Change-Id: I0c52e0c0de799cd90270794f51ad000f05122265
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak3-5/+5
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-10-11volume mount naming error in pike deployment fileSudhakar Reddy1-1/+1
Change-Id: I2b1b7e29462bea1f1511a23ff47be8ea8b033843 Issue-ID: OOM-1468 Signed-off-by: Sudhakar Reddy <Sudhakar.Reddy@amdocs.com>
2018-10-10Add pike pluginHuang Haibin4-0/+233
Change-Id: I36f00800cab85ba82ad35968b33222208ee7bc36 Issue-ID: MULTICLOUD-276 Signed-off-by: Huang Haibin <haibin.huang@intel.com>