summaryrefslogtreecommitdiffstats
path: root/kubernetes/vfc/charts/vfc-redis
AgeCommit message (Collapse)AuthorFilesLines
2020-08-25[VFC]Remove the process of mysql in vfc-redisdengyh4-15/+3
Two main process in vfc-redis: redis + mysql Issue-ID: VFC-1727 Change-Id: Ied784a4ff8270d23f3609a7942dbfb8d81e74084 Signed-off-by: dengyh <dengyuanhong@chinamobile.com>
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-04-02Bump chart versionSylvain Desbureaux1-1/+1
Use 6.0.0 in preparation for Frankfurt release Issue-ID: OOM-2320 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I8ad82dfdf48b56c38c0e85d640b18cc13c8d9e67
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-03-10Update VFC release version in oomyangyan1-1/+1
Change-Id: I57b66de5d562b5170b841c5615f84f14f75ce16a Issue-ID: VFC-1644 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-09-19Update vfc release version to oomyangyan1-1/+1
Change-Id: Ib3390afb9c1e154d9cadf9d7dc7707b35d37a8fe Issue-ID: VFC-1494 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-07-11Moving Helm Chart version for El AltoMike Elliott1-1/+1
Updating all helm chart versions to 5.0.0 for the El Alto release. Merge will be co-ordinated with the merge of a separate aai/oom patch. Please do not merge until this coordination has completed. Issue-ID: OOM-1980 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com> Change-Id: I31daaebeacea33565f13affd2fa28fb15fe948ba
2019-05-14update vfc versionyangyan1-1/+1
Issue-ID: VFC-1373 Change-Id: Id6a22594533647674dde626a013060e294e9645e Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-05-05fix vfc chart issueyangyanyj5-0/+244
Issue-ID: VFC-1374 Change-Id: I7075ea58836d5a1dafb72eeaf99f90c52d909db6 Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>