aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/vfc/charts/vfc-zte-vnfm-driver/templates
AgeCommit message (Collapse)AuthorFilesLines
2020-09-04[GENERAL] Use readiness container v3.0.1Sylvain Desbureaux1-2/+2
Readiness container v3.x and up are now present in ONAP main repository. They're also not using root user anymore and then script path has changed. Finally, "job_complete" script has been integrated in main "ready" script. As those changes are significant, we must upgrade all the components at once. Depends-On: I5afa83892043f4844afe12e61724a8d368a9f2e0 Issue-ID: OOM-2545 Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com> Change-Id: I0b4eb5dd86390273532d67d0a9696e1cfcadf110
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-12Make use msb iag with httpsyangyan2-0/+5
Change-Id: I8602f2cbe425a061470e62d2a6fc490904f42256 Issue-ID: VFC-1601 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak2-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-09-25Updating charts to use common resource templateMandeep Khinda1-1/+1
Issue-ID: OOM-1145 Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-07-31Enable istio sidecar injectio for vfcHuabing Zhao1-0/+2
Issue-ID: VFC-1003 Change-Id: I965aa3887e26c828b8d671edd6e423c33508af91 Signed-off-by: Huabing Zhao <zhaohuabing@gmail.com>
2018-04-24Make all services independent of helm Release.NameBorislavG1-4/+4
Issue-ID: OOM-906 Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-04-12VFC Communication fails because MSB service namemahendrr1-1/+1
Change-Id: I26e27cfb3b973bbffd0a94e3ec8411f5218cdf4f Issue-ID: OOM-804 Signed-off-by: mahendrr <mahendra.raghuwanshi@amdocs.com>
2018-04-10Standardized Config for VFCMike Elliott3-0/+193
Change-Id: Ie7064b59032c6cd81ee37466c89a5dee74530939 Issue-ID: OOM-750 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>