summaryrefslogtreecommitdiffstats
path: root/kubernetes/dmaap/components/dmaap-dr-node/templates/pv-aaf.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-04-16[DMaaP DR Node] v1.16+ compatible templatesSylvain Desbureaux1-54/+0
Use the different "common" templates in order to create consistent and v1.16+ compatible templates for the different resources of DMaaP DR Node. Issue-ID: OOM-1971 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I399b168882d09bd8f08148758a0f683e15ac141c
2020-03-10[DMaaP DR] Enable persistence for ClaimsSylvain Desbureaux1-3/+3
Currently, persistence was not enabled, preventing creation of relevant PV/PVC for DMaaP DR. Setting this persistence as it should be the normal behavior Issue-ID: OOM-2332 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Ic36c0956d40333529d6325af38e33a9bc6838946
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
2019-12-12[DMaaP] Use global storage templates for PVCSylvain Desbureaux1-0/+54
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 split the 3 PV from dr-node into 3 files and used range so the number of PV is the same as number of PODs. Change-Id: I46b4e62042ea8330bef8cdc1561fa8bbf3f25d12 Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>