Which operator(s) is this request for?
Why this matters
Teams running MySQL on Kubernetes today must manually track disk utilization and resize PVCs before they fill up, creating operational risk and toil. With automated storage scaling, the operator continuously monitors disk usage across all Galera cluster nodes and expands PVCs automatically when a configurable threshold is crossed, eliminating reactive firefighting. This lets platform teams set storage growth policies once in the CR and trust that the database will never run out of space, without manual intervention or downtime.
Community Note
- Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, as they generate noise and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Which operator(s) is this request for?
Why this matters
Teams running MySQL on Kubernetes today must manually track disk utilization and resize PVCs before they fill up, creating operational risk and toil. With automated storage scaling, the operator continuously monitors disk usage across all Galera cluster nodes and expands PVCs automatically when a configurable threshold is crossed, eliminating reactive firefighting. This lets platform teams set storage growth policies once in the CR and trust that the database will never run out of space, without manual intervention or downtime.
Jira: https://perconadev.atlassian.net/browse/K8SPXC-1076
Community Note