summaryrefslogtreecommitdiffstats
path: root/kubernetes/so/templates/service.yaml
AgeCommit message (Collapse)AuthorFilesLines
2023-03-06[SO] Cleanup of SO chartsAndreas Geissler1-388/+2
Remove AAF and TLS related chart entries Use OOM templates for deployment and service definitions Remove so-appc-orchestrator, as it is not supported anymore Issue-ID: OOM-3106 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I6256aa0fbbe172752cc3d8f83edde0880de7f629
2022-05-19[SO] Service mesh compatibilityAndreas Geissler1-2/+2
Patch on SO charts dedicated to allign the service port names according to Istio naming schema. Change the mariadb job to wait for the sidecar and kill it afterwards. Remove CertInitializer TLS job, if AAF is not enabled Added all missing changed from https://gerrit.onap.org/r/c/oom/+/124231 Issue-ID: OOM-2824 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I5b333ab19673ad248fd2e3bd138a99fe15025f5e
2020-10-21[SO] change comment styleJakub Latusek1-0/+2
Signed-off-by: Jakub Latusek <j.latusek@samsung.com> Change-Id: I15281199766092663aa2c0f8b96ae16979ccaa5f Issue-ID: OOM-2562
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak1-2/+2
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-10-05Update MSB annotations SO helm chart serviceRamesh Parthasarathy1-81/+81
It is assumed that all the external interfaces will go thru MSB and internal interfaces will use kube dns Change-Id: Ieb51f315e8a64af6986cd5f001d1713562154b09 Issue-ID: SO-1104 Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com>
2018-09-05helm chart for so containersRamesh Parthasarathy1-46/+363
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-04-19Fix SO healthcheck on multi-node clusterMike Elliott1-17/+17
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-03-17SO endpoints and service updateJerome Doucerain1-2/+3
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-1/+1
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-1/+1
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/+69
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>