summaryrefslogtreecommitdiffstats
path: root/kubernetes/vfc/charts
AgeCommit message (Collapse)AuthorFilesLines
2020-04-02Bump chart versionSylvain Desbureaux16-16/+16
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-27update releae version of vfc-nslcm & vfc-vnflcmyangyan2-2/+2
Change-Id: Iedfa51903c695ab29ee3060a85c1537c42335f6d Issue-ID: VFC-1644 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2020-03-25[VFC] Use faster version of common secret templateKrzysztof Opasiak8-8/+8
Issue-ID: OOM-2051 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I26c3b15e837ead96477d95312cb450a623ec16ae
2020-03-20Remove catalog component from VFCyangyan10-529/+0
Because Modeling project has created etsicatalog repo to intent to provide common ETSI catalog service, VF-C catalog migrates to modeling can help reduce duplication of work and promote unified architecture. This has reported in Architecture meeting 2019-10-15,and also been confirmed during VF-C Frankfurt Architecture Review. So the corresponding catalog chart need also be removed Change-Id: I63172ee17d8ffcdb59ac730c05d85b9a63e4d7a0 Issue-ID: VFC-1649 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2020-03-11Add VFC env about reg_to_msb_when_start to determine whether register to ↵yangyan16-2/+32
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-10Merge "Update VFC release version in oom"Krzysztof Opasiak17-17/+17
2020-03-10Update VFC release version in oomyangyan17-17/+17
Change-Id: I57b66de5d562b5170b841c5615f84f14f75ce16a Issue-ID: VFC-1644 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2020-03-09[VFC] Use common secret template for DB root passwordKrzysztof Opasiak15-30/+214
Issue-ID: VFC-1600 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I9f83c6f6eaace60c3e974218810e5943c5758c06
2020-02-12Make use msb iag with httpsyangyan32-0/+80
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 Opasiak36-81/+81
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-12-09[VFC] Use global storage templates for PVCSylvain Desbureaux2-12/+6
OOM has now templates in order to create the needed PVC, using: * a PV with a specific class when using a common nfs mount path between nodes (sames as today use) --> is the default behavior today * or a storage class if we want to use dynamic PV. On this case, we use (in order of priority): - persistence.storageClassOverride if set on the chart - global.persistence.storageClass if set globally - persistence.storageClass if set on the chart Change-Id: Ibc8825b97cbe8939cf085d1cdd17e0a67e45c96b Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-09-24change accessMode for oomyangyan1-1/+1
Change-Id: I156e5d688023d96954a106e6b6e81f7911f91e2b Issue-ID: VFC-1523 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-09-19Update vfc release version to oomyangyan7-7/+7
Change-Id: Ib3390afb9c1e154d9cadf9d7dc7707b35d37a8fe Issue-ID: VFC-1494 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-08-23Add msb environment to oomyangyan1-0/+2
Change-Id: I9c1321955c59b6f29c454aced0c00f713f5384ea Issue-ID: VFC-1467 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-07-11Moving Helm Chart version for El AltoMike Elliott17-17/+17
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-06-05update vfc release versionyangyanyj6-6/+6
Issue-ID: VFC-1396 Change-Id: I4c1a88e5dc85caef96498d8749d4a262eebe02f5 Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
2019-05-24update vfc release versionyangyan6-6/+6
Issue-ID: VFC-1396 Change-Id: Ia8617e6c54c3a504e9f68dbe34ee16f37117e26c Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-05-14update vfc versionyangyan1-1/+1
Issue-ID: VFC-1373 Change-Id: Id6a22594533647674dde626a013060e294e9645e Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-05-13update vfc image versionyangyan2-4/+4
Issue-ID: VFC-1373 Change-Id: I42af27a20622109b1ec96d6900c9e40cbb7e3970 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-05-07Merge "fix vfc chart issue"Yang Xu11-23/+7
2019-05-06update vfc juju versionyangyanyj1-1/+1
Issue-ID: VFC-1373 Change-Id: Ic5d82525b795941e23f39b6d2ee4f1959b30eec3 Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
2019-05-05fix vfc chart issueyangyanyj11-23/+7
Issue-ID: VFC-1374 Change-Id: I7075ea58836d5a1dafb72eeaf99f90c52d909db6 Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
2019-05-05update vfc image versionyangyan23-370/+16
Issue-ID: VFC-1373 Change-Id: Ia232ab4ab7b3fdddeb7777d2f756cc62f1f01410 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-04-24Merge "Update vfc chart using OOM shared mariadb galera"Borislav Glozman6-2/+22
2019-04-23Update VFC image versionYang Xu17-17/+17
Change-Id: I05c3890cf7b1cc87c575a79f0a767a4d35634161 Issue-ID: INT-1042 Signed-off-by: Yang Xu <yang.xu3@huawei.com>
2019-04-19Update vfc chart using OOM shared mariadb galerayangyan12-8/+28
Issue-ID: OOM-1776 Change-Id: I092815a6e5eebfe10cf213d995578238d73d0e48 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2019-02-25Merge "Add vfc catalog volumn"Borislav Glozman4-0/+113
2019-02-10Update Chart version for Dublin ReleaseMike Elliott18-18/+18
All charts are being bumped from 3.0.0 to 4.0.0 for the Dublin release. In addition the requirement.yaml files have been updated to allow for chart versions that include timestamp suffix. A following on patch will take care of changes to the OOM Makefiles to support injection of the timestamp versions. Change-Id: Ie03d86fad2027e975e8b9106e3a828e4335037cb Issue-ID: OOM-1642 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2019-02-03Add vfc catalog volumnyangyanyj4-0/+113
Issue-ID: OOM-1623 Change-Id: Idd9ecfaa99a7e4e8b57e12a5c442a4a1a3c3a6a0 Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
2018-11-15Sync docker tags with release manifestGary Wu13-13/+13
Sync docker tags with the release manifest from integration repo commit b37a3cfdaf92c4855660d2f0c1b20eb482b99bd4. Change-Id: Iabb203836d0c0adb5604a9303d4a108142ec6757 Issue-ID: INT-663 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-10-24Sync docker tags with release manifestGary Wu1-1/+1
Sync docker tags with the release manifest from integration repo commit 178b6b9fbab29eabee2dc05273029a560c459aa0. Change-Id: Id7f6630d356a743b3999389f2a70cbc8c69af4b7 Issue-ID: INT-663 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-10-22fix vfc deployment erroryangyan1-1/+1
Issue-ID: VFC-1160 Change-Id: I48a109c59fdee710e21c2f75e5fb0a74061f91f5 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2018-10-19Fix driver startup in OOMDenes Nemeth1-0/+2
Change-Id: Icd64543e9dcbde932852996c8b28e0e8c879c61b Signed-off-by: Denes Nemeth <denes.nemeth@nokia.com> Issue-ID: VFC-1159
2018-10-18Sync docker tags with release manifestGary Wu17-17/+17
Sync docker tags with the release manifest. It is assumed that the release manifest is the "single source of truth" and that the versions in the helm charts are out of date. Change-Id: I2902e60b25f57409dd616780a626e63c92d26769 Issue-ID: INT-663 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-10-02Add Resource Limits for vfcGregSulek18-325/+351
resolving merge conflict and aligning with resource template bumping up small/large limits so pods actually run Issue-ID: OOM-1166 Change-Id: Ied1a88f99f288544272e106677bba3f3131e48cb Signed-off-by: GregSulek <gsulek@amdocs.com> Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-09-25Updating charts to use common resource templateMandeep Khinda18-18/+18
Issue-ID: OOM-1145 Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-09-24Update Chart versions to 3.0Mike Elliott18-18/+18
All Chart versions and requirement dependencies have been updated to 3.0 for Casablanca release. Change-Id: Iea57e5da09ea8a8bac0a415b9a6196151cbea10b Issue-ID: OOM-1354 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-09-19Sync values from docker-manifest-staging fileAlexis de Talhouët1-1/+1
Change-Id: Ic8f11dc20c425aab144fe28a5e761552eb7b025b Issue-ID: OOM-1422 Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
2018-08-20Merge "Add VFC DB helm charts"Borislav Glozman10-75/+324
2018-08-17Modify vfc values.yamlyangyan17-17/+17
Issue-ID: VFC-1031 Change-Id: Icab173a0927d3b82ea38733b6541e197ae01930f Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2018-08-16Add VFC DB helm chartsBharath Thiruveedula10-75/+324
Issue-ID: VFC-975 Change-Id: I03534929bfa30efb22354d044d19b1459718ac11 Signed-off-by: Bharath Thiruveedula<bharath.thiruveedula@verizon.com>
2018-07-31Enable istio sidecar injectio for vfcHuabing Zhao34-0/+85
Issue-ID: VFC-1003 Change-Id: I965aa3887e26c828b8d671edd6e423c33508af91 Signed-off-by: Huabing Zhao <zhaohuabing@gmail.com>
2018-06-05Sync OOM docker versions with docker-manifest.csvGary Wu17-17/+17
Sync OOM docker versions with docker-manifest.csv commit a6e05c8c18624a1794abb1d3a3ab879a7a06bcfe Change-Id: If8df538638670e0f1080d41d40d06de54ab1d93a Issue-ID: OOM-1053 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-05-10Improve docker registry secret managementBorislavG17-17/+0
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d Issue-ID: OOM-1064 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-05-08Sync docker image images with docker-manifest.csvGary Wu16-16/+16
Update the docker image versions in the OOM helm charts with the versions specified in the docker-manifest.csv in the integration repo. Change-Id: I38bd9e98ae1b15ed4bbc68051b8516f311aa8db0 Issue-ID: OOM-1053 Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
2018-04-24Make all services independent of helm Release.NameBorislavG34-70/+87
Issue-ID: OOM-906 Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-04-24Merge "Update vfc charts configutation"Mandeep Khinda3-1/+10
2018-04-18Update vfc charts configutationyangyan3-1/+10
Change-Id: I79dc1c5d26692fe675ca4cf2779fc78eac557a45 Issue-ID: VFC-879 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
2018-04-17Change the service name of MSB register annotationLiZi1-1/+1
The service name of vfc-workflow and vfc-workflow-engine are both "workflow" in MSB register annotations. Actually they are two different service. Change-Id: I45bb3a131431bb4893c0dc992cdb008c1045cf84 Issue-ID: OOM-949 Signed-off-by: LiZi <li.zi30@zte.com.cn>
2018-04-16Update readiness-check versionBorislavG17-17/+17
Readiness check version is not sinchronized in many pods This causing deployment failures. Issue-ID: OOM-936 Change-Id: Ieef91df17836adcdf24db536440d0a1624a50591 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>