[installer] mysql helm global.storageClass may need to be set

[metcalfc]

I set a default storage class:

kubectl patch storageclass local-path -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

minio and registry respect that. mysql does not. In the Bitnami Helm chart the option is:

global.storageClass and by default its nil

When we render it down we might have to give it a value?

[metcalfc]

I tried adding a StorageClassName on the volumeClaimTemplates:

  volumeClaimTemplates:
    - metadata:
        name: data
        labels:
          app.kubernetes.io/name: mysql
          app.kubernetes.io/instance: MySQL
          app.kubernetes.io/component: primary
      spec:
        accessModes:
          - "ReadWriteOnce"
        resources:
          requests:
            storage: "5Gi"
        storageClassName: "local-path"

Its not flowing through to the StatefulSet.

 k describe pvc data-mysql-0
Name:          data-mysql-0
Namespace:     default
StorageClass:
Status:        Pending
Volume:
Labels:        app.kubernetes.io/component=primary
               app.kubernetes.io/instance=MySQL
               app.kubernetes.io/name=mysql
Annotations:   <none>
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       mysql-0
Events:
  Type    Reason         Age                  From                         Message
  ----    ------         ----                 ----                         -------
  Normal  FailedBinding  25s (x142 over 35m)  persistentvolume-controller  no persistent volumes available for this clai

I've also set a default storageclass. So I would have thought it would have just been picked up.

k describe storageclasses.storage.k8s.io
Name:            local-path
IsDefaultClass:  Yes

[metcalfc]

Kubernetes is a journey.

We should likely require a default storage class or let folks set it.

[metcalfc]

Gitlab has a nice example to follow.

https://docs.gitlab.com/charts/installation/storage.html#using-the-custom-storage-class

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[lucasvaltl]

@Pothulapati could you take a look at this? This might be related to the work you are doing regarding post-processing in the #9075 and if we have a good fix there it might help with this issue as well.

[lucasvaltl]

@mrsimonemms could you please also check here if this is still relevant?

[mrsimonemms]

I'm going to close this as "not planned". There's been no other mention of this since November as in-cluster MySQL has sort of evolved as the backup choice - the preferred, enterprise-grade solution is always to use a managed/external database.