diff options
| author |   Sylvain Desbureaux <sylvain.desbureaux@orange.com> | 2019-12-09 11:06:39 +0100 |
|---|---|---|
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | 2019-12-16 10:54:45 +0100 |
| commit | 25e01d5ab10a68ec4689e4860edcf3c9640d1586 (patch) | |
| tree | 4fc841a64dc0e036121e3be85649a706e251e845 /kubernetes/sdc/charts/sdc-onboarding-be/templates/pvc.yaml | |
| parent | 72c71c0b832a169c03bcdbaa5997956e30f62c7c (diff) | |
[SDNC] 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 used "range" for PV creation of the statefulset
I've created one file per PV (one for mdsal, one for certs).
sdnc-prom was using hostpath directly on deployment, move to a PV/PVC.
Change-Id: Id9eed3b13ac85595c386e380f41cfbc38b52c69f
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Diffstat (limited to 'kubernetes/sdc/charts/sdc-onboarding-be/templates/pvc.yaml')
0 files changed, 0 insertions, 0 deletions