summaryrefslogtreecommitdiffstats
path: root/kubernetes/vfc/charts/vfc-catalog/templates/pv.yaml
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-12-09 11:36:11 +0100
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2019-12-09 11:37:11 +0100
commit34b8d99bb80baeb49f5b7142dbe79e43e967b8b3 (patch)
tree138e2fbdd8fb1b11f9a8e2d9f5ffd8a0881b805b /kubernetes/vfc/charts/vfc-catalog/templates/pv.yaml
parent72c71c0b832a169c03bcdbaa5997956e30f62c7c (diff)
[PNDA] 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 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>
Diffstat (limited to 'kubernetes/vfc/charts/vfc-catalog/templates/pv.yaml')
0 files changed, 0 insertions, 0 deletions