diff options
| author |   Jerome Doucerain <jerome.doucerain@bell.ca> | 2018-04-13 12:24:53 -0400 |
|---|---|---|
| committer | Jerome Doucerain <jerome.doucerain@bell.ca> | 2018-04-19 14:09:55 +0000 |
| commit | dee57fd5c546ee0b68d3e6c003cdc06ada987abe (patch) | |
| tree | da1f2fca16e1bc42ef95fd18e8cc27ba41fa2ec0 /kubernetes/sdnc/values.yaml | |
| parent | 7ce74aca0ce63ba4336fad7161e30ba791906e22 (diff) | |
fix nfs-provisioner for appc and sdnc
change in common/mysql/templates/pvc.yaml to allow pvc use
when persistence is required
change in common/mysql/templates/storageclass.yaml to be
led by the disableNfsprovisioner variable
change in appc/values to default the disableNfsprovisioner
to false as it is in sdnc
changing the default disableNfsprovisioner to true for both appc and sdnc
changing the stateful set avoid volumeclaimtemplates.
When used in helm, the volumeclaimtemplates is causing pvc to be left
after the helm delete --purge. I guess this is due to the fact the pvc
are not directly created by the helm install by indirectly by kubernetes
Now the tests are working in both cases (nfsprovisioner disabled or not)
The only piece remaining after a helm delete is pv in released state
in case we are using nfsprovisioner. That makes sense again because this
are objects created by the provisioner and not by helm.
removed some leftover
Issue-ID: OOM-787
Change-Id: Ieb1f1c482217aeb1b89be39a437bb891a299db71
Signed-off-by: Jerome Doucerain <jerome.doucerain@bell.ca>
Diffstat (limited to 'kubernetes/sdnc/values.yaml')
| -rw-r--r-- | kubernetes/sdnc/values.yaml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/kubernetes/sdnc/values.yaml b/kubernetes/sdnc/values.yaml index 8de608b3c6..6360d37e21 100644 --- a/kubernetes/sdnc/values.yaml +++ b/kubernetes/sdnc/values.yaml @@ -80,7 +80,7 @@ mysql: persistence: mountSubPath: sdnc/data enabled: true - disableNfsProvisioner: false + disableNfsProvisioner: true replicaCount: 1 dgbuilder: |