Which operator(s) is this request for?
Why this matters
Major database version upgrades are among the highest-risk operations a team performs, typically requiring maintenance windows, deep DBA expertise, and manual coordination across every cluster node. Without operator-level automation, organizations running PXC on Kubernetes are left to orchestrate these upgrades themselves, increasing the chance of data loss, extended downtime, or a failed upgrade leaving the cluster in an inconsistent state. Automating major version upgrades directly in the operator lowers operational risk, reduces the expertise required, and helps teams stay current on supported MySQL versions without disrupting production workloads.
Jira: https://perconadev.atlassian.net/browse/K8SPXC-1824
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
Major database version upgrades are among the highest-risk operations a team performs, typically requiring maintenance windows, deep DBA expertise, and manual coordination across every cluster node. Without operator-level automation, organizations running PXC on Kubernetes are left to orchestrate these upgrades themselves, increasing the chance of data loss, extended downtime, or a failed upgrade leaving the cluster in an inconsistent state. Automating major version upgrades directly in the operator lowers operational risk, reduces the expertise required, and helps teams stay current on supported MySQL versions without disrupting production workloads.
Jira: https://perconadev.atlassian.net/browse/K8SPXC-1824
Community Note