aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/so/templates/deployment.yaml
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-29[SO] Make SO compatible with Kubernetes v1.17Grzegorz-Lis1-1/+4
Issue-ID: OOM-2467 Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com> Change-Id: I30867bd37e649053b97dec023cc405b4d70d1adc
2020-03-31[SO] Onboard ONAP CA during init phaseSylvain Desbureaux1-4/+5
Workaround for retrieving ONAP root CA and keeping SO container being run by no root user. Issue-ID: SO-2730 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Ib1b48c0a6fcca359a780640b8c705e75fd78dc1a
2020-03-28[SO] Use common secret template in soKrzysztof Opasiak1-16/+4
Generate passwords for: - so_user - so_admin and distribute them to all SO subcharts. mariadb-galera root password is taken as a reference to existing secret (shared mariadb instance) or also generated if local cluster is used. Three other DB users also have generated passwords but they are not distributed outside of so-mariadb as they were never used. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ic4af5c9b12b00d2a52d2597e3fe1161d0d1a9f20
2020-02-25readd so filebeat sidecar ELK endpointsunilb1-0/+26
Issue-ID: SO-1110 Signed-off-by: sunilb <sb00577584@techmahindra.com> Change-Id: Ic468a1b28d681d14e862f4405890d996b42660f6
2020-02-07These OOM changes are related AAF IntegrationRamesh Parthasarathy1-10/+17
Here we have the ability to optionally disable AAF integration. A global variable global.security.aaf.enabled=true will turn on AAF security. with global.security.aaf.enabled=false it will use spring.security to ensure backward compatibilty. updated based on review comments Issue-ID: SO-2452 Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com> Change-Id: Ia83622ad681cfd122ee906ccd1654b10b5e31fe4
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak1-9/+9
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-04-19SO Rolling upgrade using helm hooksMahendra Raghuwanshi1-3/+3
Issue-ID: OOM-1772 Change-Id: If206ae7cc2f4273889376e1bb3fa77bacfaae3cc Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
2018-10-12Added missing maria db dependenciesjmac1-1/+16
If there are other inter-pod dependencies that should be managed, please comment to let me know so they can be added. Also addressed the missing globals section in the pods values.yaml files and incorrect pull policy management to make them follow the standard conventions Change-Id: I3625f8452d90182391e1ff4af5fddfe9d0948a32 Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: OOM-1472
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-09-20SO helm chart cleanupRamesh Parthasarathy1-29/+0
SO helm chart has been cleaned up and theseZ changes have been verified with SO rancher env Change-Id: If6a26f5c346f77936aeaf4102341f14759714bf1 Issue-ID: SO-1073 Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
2018-09-19Do not mount certificates in SOAlexis de Talhouët1-6/+0
Certififacte has been added in the base docker image, https://gerrit.onap.org/r/#/c/66209/ so no need to add it again. Also, it was being mount at the wrong place. Also, using latest docker images. Change-Id: I55355dac9bfb2691f493317f77c0f363a78af7ee Issue-ID: OOM-1407 Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
2018-09-07Flavors defintion in resource limitvaibhav16dec1-7/+2
Issue-ID: OOM-1322 Change-Id: I5248ae206da6b5d65b0830f454813e6e14ec7284 Signed-off-by: vaibhav16dec <vaibhav.chopra@amdocs.com>
2018-09-05helm chart for so containersRamesh Parthasarathy1-162/+112
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-05-10Add onap crtBrian Freeman1-0/+3
Issue-ID: OOM-1068 Change-Id: I7ff15fa9eb6c29852c089ad10e0c63faba05fe00 Signed-off-by: Brian Freeman <bf1936@att.com>
2018-05-10removing obsolete configmaps from SOMandeep Khinda1-19/+0
The presence of these disrupts the SO boot process resulting in the misconfiguration found by the defect Issue-ID: OOM-1052 Change-Id: I527698c6ccbdd42b3435ca33dc97cb09da7afd97 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-05-09Add new onap ca cert to SOMike Elliott1-2/+2
Swapping out aai.crt for onap-ca.crt. Change-Id: I4537fcc02c17ed19a0b3c5fa3581037c9999dd5c Issue-ID: OOM-1068 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-05-08reducing configmap for SOMandeep Khinda1-1/+1
-cloning project files during pod init-phase -injecting SQL through a shared volume Issue-ID: OOM-858 Change-Id: Idc845910d5386c3228fb9a557fb3238823242cea Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-19Fix SO healthcheck on multi-node clusterMike Elliott1-5/+5
Aligned service names (and numerous other minor fixes) with latest best practices and standard templates. Change-Id: I740fe299053805df60abcd6a6043031d8beda7e8 Issue-ID: OOM-909 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-04-17Fix SO HealthcheckBorislavG1-0/+18
Change-Id: Ia742842cf1878c5786f71949013ed8afedd13c39 Issue-ID: OOM-909 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-03-17SO endpoints and service updateJerome Doucerain1-1/+2
updated the endpoints and service in a single namespace onap deployment prospective updated the parameters order for the image source to allow override Issue-ID: OOM-743 Change-Id: I6a379ec4661d465f95478b383d60c3b2eecc0f72 Signed-off-by: Jerome Doucerain <jerome.doucerain@bell.ca>
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-3/+3
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-03-06make so chart one namespace compatiblekerenj1-3/+3
changed namespace to be nsPrefix only added component name as prefix to chart name changed all templated to use name instead of fullname Issue-ID: OOM-784 Change-Id: If2288ba14e5f74a7f7ba4c2f9bf46eecc36feca7 Signed-off-by: kerenj <keren.joseph@amdocs.com>
2018-02-23Add standardized helm chart for soMike Elliott1-0/+177
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>