-
Task
-
Resolution: Unresolved
-
Medium
-
None
In the Operator based DB creation for cassandra and mariadb
currently the "storageClassName" is defined in the values.yaml:
k8ssandraOperator:
cassandraVersion: 4.0.10
persistence:
#storageClassName: default
size: 10Gi
mariadbOperator:
image: mariadb
appVersion: 11.1.2
persistence:
#storageClassName: default
size: 3Gi
Additionally there redundant "persistance" entries in values.yaml:
persistence: ... ## Persistent Volume Storage Class ## If defined, storageClassName: <storageClass> ## If set to "-", storageClassName: "", which disables dynamic provisioning ## If undefined (the default) or set to null, no storageClassName spec is ## set, choosing the default provisioner. (gp2 on AWS, standard on ## GKE, AWS & OpenStack) ## # storageClass: "-" ... ## Persistent Volume size ## size: 3Gi
and in the "global" section:
# default mount path root directory referenced # by persistent volumes and log files persistence: mountPath: /dockerdata-nfs enableDefaultStorageclass: false parameters: {} storageclassProvisioner: kubernetes.io/no-provisioner volumeReclaimPolicy: Retain
which is used in the common template (see https://git.onap.org/oom/tree/kubernetes/common/common/templates/_storage.tpl)
we should use the same mechanism in the cassandra and mariaDB templates...