You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cannot scale up pxc and proxysql instances storage from the CR definition of the pxc cluster
More about the problem
If we try to increase the size of the pxc instances storage defined in the spec.pxc.volumeSpec.persistentVolumeClaim.resources.requests.storage CR attribute, the cluster switch to error state because the operator try to update the related attribute in the pxc statefulset but this operation is prevented as we can see from the operator logs :
"Forbidden: updates to statefulset spec for fields other than …"
If we try to apply the same operation for the proxysql instances storage defined in the spec.proxysql.volumeSpec.persistentVolumeClaim.resources.requests.storage, nothing happens.
As far as I know, the only way to scale up the storage size of these instances is to directly update the related pvc definition, assuming that these pvc are provided by storageclasses allowing the volume expansion of course. But this is not very convenient as the CR definition and related statefulsets are not updated behind.
It would be a great improvement to allow volume expansion from the CR definition by creating external pvc attached to the pod using Claims As Volumes method as implemented with the PostgreSQL operator instead of the dynamic pvc creation from statefulset definition with the Volume Claim Templates method.
Steps to reproduce
1 - Create a pxc cluster with proxysql section enabled and define a specific storage request size for both pxc and proxysql section
2 - Wait for the cluster to be ready and see that pvc were created with the desired storage sizes
3 - Edit the pxc CR definition by increasing spec.pxc.volumeSpec.persistentVolumeClaim.resources.requests.storage attribute
4 - See the cluster switching to error state and the related log errors from the operator pod. Pvc are not scaled up
5 - Revert the change in the CR definition
6 - The cluster is back to ready state
7 - Edit the pxc CR definition by increasing spec.proxysql.volumeSpec.persistentVolumeClaim.resources.requests.storage attribute
8 - See that nothing happen, operator do not take any action and pvc are not scaled up
Versions
1 - Kubernetes - v1.27.6
2 - Operator - Percona Operator for MySQL based on Percona XtraDB Cluster 1.13.0
3 - Database - MySQL XtraDB 8.0
Anything else?
1 - Kubernetes - v1.27.6
2 - Operator - Percona Operator for MySQL based on Percona XtraDB Cluster 1.13.0
3 - Database - MySQL XtraDB 8.0
The text was updated successfully, but these errors were encountered:
Report
Cannot scale up pxc and proxysql instances storage from the CR definition of the pxc cluster
More about the problem
If we try to increase the size of the pxc instances storage defined in the spec.pxc.volumeSpec.persistentVolumeClaim.resources.requests.storage CR attribute, the cluster switch to error state because the operator try to update the related attribute in the pxc statefulset but this operation is prevented as we can see from the operator logs :
"Forbidden: updates to statefulset spec for fields other than …"
If we try to apply the same operation for the proxysql instances storage defined in the spec.proxysql.volumeSpec.persistentVolumeClaim.resources.requests.storage, nothing happens.
As far as I know, the only way to scale up the storage size of these instances is to directly update the related pvc definition, assuming that these pvc are provided by storageclasses allowing the volume expansion of course. But this is not very convenient as the CR definition and related statefulsets are not updated behind.
It would be a great improvement to allow volume expansion from the CR definition by creating external pvc attached to the pod using Claims As Volumes method as implemented with the PostgreSQL operator instead of the dynamic pvc creation from statefulset definition with the Volume Claim Templates method.
Steps to reproduce
1 - Create a pxc cluster with proxysql section enabled and define a specific storage request size for both pxc and proxysql section
2 - Wait for the cluster to be ready and see that pvc were created with the desired storage sizes
3 - Edit the pxc CR definition by increasing spec.pxc.volumeSpec.persistentVolumeClaim.resources.requests.storage attribute
4 - See the cluster switching to error state and the related log errors from the operator pod. Pvc are not scaled up
5 - Revert the change in the CR definition
6 - The cluster is back to ready state
7 - Edit the pxc CR definition by increasing spec.proxysql.volumeSpec.persistentVolumeClaim.resources.requests.storage attribute
8 - See that nothing happen, operator do not take any action and pvc are not scaled up
Versions
1 - Kubernetes - v1.27.6
2 - Operator - Percona Operator for MySQL based on Percona XtraDB Cluster 1.13.0
3 - Database - MySQL XtraDB 8.0
Anything else?
1 - Kubernetes - v1.27.6
2 - Operator - Percona Operator for MySQL based on Percona XtraDB Cluster 1.13.0
3 - Database - MySQL XtraDB 8.0
The text was updated successfully, but these errors were encountered: