aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/pnda/charts/dcae-pnda-bootstrap/templates
AgeCommit message (Collapse)AuthorFilesLines
2020-10-29[Tree-wide] Remove pnda charts from OOMKrzysztof Opasiak4-212/+0
pnda was introduced in earlier release (R3) as POC however no longer supported. As we don't like unmaintained code and noone is using it let's remove it from oom helm charts. Issue-ID: DCAEGEN2-2503 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I717925acee3956ac7e5c6abda7a54e3a78f3ebf3
2020-10-21[PNDA] change comment styleJakub Latusek2-0/+4
Signed-off-by: Jakub Latusek <j.latusek@samsung.com> Change-Id: I3d9cd7715753364d2e9c9c90cc16e48d41569056 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 Opasiak3-5/+5
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[PNDA] Use global storage templates for PVCSylvain Desbureaux3-16/+47
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 PVC for the job instead of doing a PVC template inside the job. Change-Id: I0cc242db0b1412ac792dec74a6542849c30985c9 Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2018-09-25Add PNDA bootstrap job to dcaegen2 chartDonald Hunter3-0/+177
Change-Id: I39974a948d261e3e6d80faf0219f67d4ffc8c90c Issue-ID: DCAEGEN2-779 Signed-off-by: Donald Hunter <donaldh@cisco.com>