summaryrefslogtreecommitdiffstats
path: root/kubernetes/so/requirements.yaml
AgeCommit message (Collapse)AuthorFilesLines
2021-03-24[DOC][COMMON] Prepare Honolulu releaseSylvain Desbureaux1-21/+21
Updating the documentation and bumping version to 8.0.0 Issue-ID: OOM-1 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I6f942f1466fed64264c44fb8fc0e1ffc93a98f18
2020-11-30[COMMON][DOC] Bump version GuilinSylvain Desbureaux1-21/+21
Update charts and requirements to 7.0.0. Create release notes for Guilin Update documentation Issue-ID: OOM-2638 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I965ed6b6ebb7d74bfddaff73edd3dd55a657841c
2020-11-27[SO] helm chart for cnf-adaptersekharhuawei1-0/+4
Add helm chart for cnf-adapter to oom Issue-ID: SO-3164 Signed-off-by: sekharhuawei <reddi.shekhar@huawei.com> Change-Id: Ib96c130b05d31a11e42603300f5e7e0f43cb9aa1 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-11-21[SO] Uses new tpls for repos / imagesSylvain Desbureaux1-0/+3
This commit makes SO chart to use the new generator for repositories and images. Issue-ID: OOM-2364 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Ife4e1fcfff565b3ada7e726913826e2c9f76bc07
2020-11-05Revert "[SO] helm chart for cnf-adapter"Sylvain Desbureaux1-19/+15
This reverts commit a2145f7fa5a4bfadf6782333a879e75730da4f8e. Reason for revert: it seems to have weird consequences when bumping so version Issue-ID: SO-3164 Change-Id: Ibf869be9e9dcba915a738605af6d4f823742fbea Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-11-02[SO] Use readiness chartSylvain Desbureaux1-1/+4
Some SO components are using readiness check init container. In "gating" mode, so image and readiness image are not coming from the same repository. By using readinessCheck charts, we can control that. Issue-ID: OOM-2617 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I44a4e9daf72d1a42d3d84b6d56b588cd7d44fb08
2020-11-02[SO] Remove so-db-secretskrishnaa961-4/+0
so-db-secrets was used to create secrets for db creds. But now, they are being created from secrets metaconfig. It is not needed Issue-ID: OOM-2534 Signed-off-by: Krishna Moorthy <krishna.moorthy6@wipro.com> Change-Id: I0f0514b0b704e4643253b793ea4bd9ad92329759
2020-11-02[SO] Remove so-secret componentSylvain Desbureaux1-3/+0
SO secret was used to give truststore to SO components. As we're using dynamic certificate retrieval, it's not needed anymore. Issue-ID: OOM-2534 Issue-ID: SO-3348 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I0eb2e052096923fc69bf5f1a1876d9a76a22102b
2020-10-30[SO] helm chart for cnf-adaptersekharhuawei1-18/+22
Add helm chart for cnf-adapter to oom Issue-ID: SO-3164 Signed-off-by: sekharhuawei <reddi.shekhar@huawei.com> Change-Id: I12551f8403c55b7f0d0e54dea0d003413039b6a6 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-10-19Merge "[SO] Add charts for so-oof-adapter"Sylvain Desbureaux1-0/+4
2020-10-16[SO] Add helm chart for SO-ETSI-NFVO-NS-LCMAndrewLamb1-0/+4
This chart for SO-3157 was previously merged here: https://gerrit.onap.org/r/c/oom/+/111378 It was subsequently reverted here: https://gerrit.onap.org/r/c/oom/+/112538 due to use of staging image It could then not be re-introduced until other OOM problems were fixed. Chart has been updated in line with changes made here: https://gerrit.onap.org/r/c/oom/+/111328 Also included, SO-3225 - small change from this review: https://gerrit.onap.org/r/c/oom/+/112358 which could not be merged due to other oom problems, and then also due to revert. Once this is merged, I will abandon old review at: https://gerrit.onap.org/r/c/oom/+/112358 Issue-ID: SO-3157 Change-Id: I3b59b9f655b395d7a22ea06814004baeb158b7d7 Signed-off-by: AndrewLamb <andrew.a.lamb@est.tech> Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-10-14[SO] Add charts for so-oof-adapterPriyadharshini1-0/+4
Issue-ID: SO-3205 Signed-off-by: Priyadharshini <priyadharshini.b96@wipro.com> Change-Id: Ic25f2a1421cc7a2370f1793b6c6735a55b4d78c9
2020-10-12[SO] move subcharts to components folderseshukm1-0/+58
Move subcharts to components folder in order to be able to enable/disable them one by one. Also use certInitializer to retrieve truststore in order to be able to discuss with other ONAP components. Issue-ID: SO-2046 Change-Id: Ia5c2a590a2ad75e4b69be0748e9d79fda996af37 Signed-off-by: seshukm <seshu.kumar.m@huawei.com> Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-04-02Bump chart versionSylvain Desbureaux1-2/+2
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
2019-07-11Moving Helm Chart version for El AltoMike Elliott1-2/+2
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-04-19SO Rolling upgrade using helm hooksMahendra Raghuwanshi1-1/+5
Issue-ID: OOM-1772 Change-Id: If206ae7cc2f4273889376e1bb3fa77bacfaae3cc Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
2019-02-10Update Chart version for Dublin ReleaseMike Elliott1-1/+1
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>
2018-09-24Update Chart versions to 3.0Mike Elliott1-1/+1
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-05helm chart for so containersRamesh Parthasarathy1-1/+0
This check-in is an updated version of helm charts for so containers based on review comments Change-Id: I690430622ecbdcaf099a6165844142841db436dd Issue-ID: SO-709 Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
2018-03-22License addition in all yamlsvaibhav_16dec1-0/+14
Issue-ID: OOM-821 Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
2018-03-09iterating on new helm structure for SOMandeep Khinda1-2/+2
with this change we can now do the following: can deploy umbrella chart with currently working components: helm install local/onap --name onap --namespace onap-all helm install local/onap --name onap-2 --namespace onap-all-2 \ --set global.nodePortPrefix=303 - umbrella includes setup chart can deploy a-la-carte component by component into a single namespace - Need to deploy a setup chart first. cannot be made a helm dependency as there will be conflicts if each app chart has the same setup dependency. helm install local/setup --name onap-setup --namespace onap-apps helm install local/so --name so1 --namespace onap-apps \ --set global.nodePortPrefix=304 helm list NAME REVISION STATUS CHART NAMESPACE onap 1 DEPLOYED onap-2.0.0 onap-all onap-2 1 DEPLOYED onap-2.0.0 onap-all-2 onap-setup 1 DEPLOYED setup-2.0.0 onap-apps so1 1 DEPLOYED so-2.0.0 onap-apps Unfortunately, the config maps all have fixed names, so installing the same app in the a-la-carte fashion will fail due to a collision. Not worrying about this as I'm not sure we want to support this. -made the common and setup charts standalone to remove relative file paths from requirements.yaml This will help when there are different levels of subcharts that need to include common Issue-ID: OOM-786 Issue-ID: OOM-789 Issue-ID: OOM-788 Change-Id: I20bacae6f0f20e8f3bb1527af1e7e53f187341d5 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-02-23Add standardized helm chart for soMike Elliott1-0/+7
This is a standardization (based on helm community best practices) of a Helm chart for the Service Orchestrator (so) in ONAP. How to deploy the so chart (outside of the parent onap chart) from the local oom/kubernetes codebase. ** need to create/update dependencies defined in the chart's ** requirements.yaml helm dep update so/ ** deploy the so helm chart with the "release" name of 'onap' helm install so/ -n onap Change-Id: I22471eb9fe0dec32941e14dc63857222c80ebe20 Issue-ID: OOM-727 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>