summaryrefslogtreecommitdiffstats
path: root/kubernetes/vfc/charts/vfc-redis/templates
AgeCommit message (Collapse)AuthorFilesLines
2020-07-30[VFC] Make VFC compatible with Kubernetes v1.17Grzegorz-Lis1-1/+4
Issue-ID: OOM-2469 Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com> Change-Id: Ib7c794cca28ac2494eedba31903dcbd9348820c7
2020-03-11Add VFC env about reg_to_msb_when_start to determine whether register to ↵yangyan1-0/+2
microserice Becaue now oom can register the microservice to msb automatically, if without K8S, we can also register vfc microservice to msb automatically by vfc container itself. IF it is set to false, vfc contanier will not register again, if it is set to true, vfc will register by itself. we use this flag to determine who is responbile for serice registeration and it can reduce duplicate registration. Change-Id: Ie79a8803725ae0c762d9c39a04f922d9823c46e2 Issue-ID: VFC-1601 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak2-4/+4
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-05-05fix vfc chart issueyangyanyj2-0/+117
Issue-ID: VFC-1374 Change-Id: I7075ea58836d5a1dafb72eeaf99f90c52d909db6 Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>