Helm: MySQL storageClass accepted but not being used in deployment

[Nickmman]

Description:
Deploying 4.1.x via helm, configured the following so MySQL uses a non-NFS storageClass:

    mysql-am:
      mysql:
        persistence:
          storageClass: "ceph-filesystem"

The PVC gets properly created, however since it's using the bitnami image, /var/lib/mysql (where the PVC is mounted) is not used. Instead, bitnami mounts the datadir under /bitnami/mysql/data/, which falls under the ephemeral storage of the pod. When the pod is recycled, the database is wiped, since nothing was written to the PVC where it was mounted, thus incurring data loss.

Suggested Labels:
Severity/Critical,Type/Bug,Priority/Highest

Suggested Assignees:
@RakhithaRR

Affected Product Version:
4.1.x (deployed) and assuming others

OS, DB, other environment details and versions:
GCP GKE v1.26.8, deploying using Helm via ArgoCD

Steps to reproduce:

1. Deploy WSO2 4.1.x using helm, specify persistence storage class
2. Check that PVC is created using specified storage class
3. Inside the container, verify that the mount location for the PVC is not the directory where the MySQL server is storing the data

Related Issues:

[Nickmman]

@PasanT9 Tagging you as well since I've seen you active on PRs lately. This really needs to be looked at.

[yuniet87]

Happen the same here...