summaryrefslogtreecommitdiffstats
path: root/kubernetes/cds/charts/cds-blueprints-processor/templates/pv.yaml
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-11-29 15:55:11 +0100
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-12-12 16:46:36 +0100
commit60141128dc3b8224b9f414c599d3c8826574c45c (patch)
treedbb31ad01dd60958ad28106595435d46056b119a /kubernetes/cds/charts/cds-blueprints-processor/templates/pv.yaml
parent9b0adea0769b026875ee312d223960c559c700bb (diff)
[DMaaP] Use global storage templates for PVC
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>
Diffstat (limited to 'kubernetes/cds/charts/cds-blueprints-processor/templates/pv.yaml')
0 files changed, 0 insertions, 0 deletions