aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/pomba/charts/pomba-data-router/templates
AgeCommit message (Collapse)AuthorFilesLines
2020-10-21[POMBA] change comment styleJakub Latusek4-0/+8
Signed-off-by: Jakub Latusek <j.latusek@samsung.com> Change-Id: I8c8f00e22a39113e5f3daf8d04204a99eab8139d Issue-ID: OOM-2562
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-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak4-8/+8
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-12[POMBA] Use global storage templates for PVCSylvain Desbureaux2-10/+5
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 I've also created a PV/PVC couple for logs of ES as it was hardcoded in the deployment. Change-Id: Ic2da694da008803f5afc1a0e0de38a1428c5b40e Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-11-28Add ingress controler support to POMBALucjan Bryndza1-0/+1
Issue-ID: OOM-2184 Change-Id: I75f7e8239fe1f1027fffae6b3e2a848a593351ae Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
2019-03-13Add missing filebeat sidecars for Pombajmac1-0/+19
Change-Id: I5f2cf1d74d55df0002af75367042eaf795ea2e8c Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: LOG-852
2018-11-27Set resource limits/requests for POMBA data routerSylvain Desbureaux1-0/+2
Using in POMBA data router resources flavors (small, large and unlimited) set in values.yaml into deployment.yaml Change-Id: I48fcba823b8c23e76432693c91c8ec896d85a0a0 Issue-ID: LOG-857 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2018-10-23Add missing resource limits to POMBA podsjmac1-0/+14
Add missing pod dependencies Change-Id: Id976b00e6e0d0c325d93f3e3b77b757e2c72b378 Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: OOM-1465
2018-08-29Add Pomba Data Router to OOMJennie Jia6-0/+319
Issue-ID: LOG-589 Change-Id: I0ce093983997379bb94c21bb0361b5d23ec2f994 Signed-off-by: Jennie Jia <Jennie.Jia@amdocs.com>