Bug #111269 Increasing pvc storage request amount has no effect
Submitted: 5 Jun 2023 0:13 Modified: 5 Jun 2023 15:32
Reporter: Linus H. Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Operator Severity:S3 (Non-critical)
Version:8.0.33-2.0.10 OS:Linux
Assigned to: CPU Architecture:x86

[5 Jun 2023 0:13] Linus H. 
Description:
I should be able to increase the pvc sizes by changing the helm values of mysql-innodbcluster, after it was deployed.

When first deploying the mysql-innodbcluster helm chart with

datadirVolumeClaimTemplate.resources.requests.storage = "1Gi"

and increasing it to for example

datadirVolumeClaimTemplate.resources.requests.storage = "2Gi"

has no effect on the pvc or corresponding pv, in my case managed by csi-cinder-high-speed storage class in a working OpenStack environment at OVHcloud.

Other pvc size increments, as tested with bitnami/minio, work flawlessly.

How to repeat:
Increasing the storage request size inside the datadirVolumeClaimTemplate to a higher value, after the chart mysql-innodbcluster was successfully installed.
[5 Jun 2023 0:35] Linus H. 
Editing the required storage amount via
kubectl edit persistentvolumeclaim/datadir-mysql-innodbcluster-0
directly, also works. This needs to be done by the helm chart.
[5 Jun 2023 15:32] MySQL Verification Team 
Thank you for report