PXC 8.0 to 8.4 on OpenShift 4.14 now, 4.22 later: which operator version and upgrade path?

MySQL & MariaDB Percona Operator for MySQL
1

Description:

Hi @Slava_Sarzhan @Valmira_Nogueira,

We plan the move from PXC 8.0 to 8.4 and would like Percona’s guidance on the operator version and the upgrade path. The platform’s next OpenShift version is 4.22 or later. It redeploys the cluster and skips 4.15 to 4.21.

What we found so far:

Questions:

  1. Is an operator release planned that is tested on OpenShift 4.22, with PXC 8.4 GA? Which version, and roughly when?
  2. On OpenShift 4.14, would Percona support operator 1.19 or 1.20 with PXC 8.4, outside the tested range? If not, is operator 1.17 with the 8.4 tech preview the only option there?
  3. When OpenShift jumps from 4.14 to 4.22 with a cluster redeploy, what is the supported path for the operator: a fresh install of the newest certified operator on 4.22, then a restore of a backup taken by the older operator?
  4. For 8.0 to 8.4, is this method supported: create a new PXC 8.4 cluster and restore an operator-made backup of the 8.0 cluster into it? Which XtraBackup version should prepare that backup?
  5. PXC 8.0 is EOL since April 2026. Does post-EOL support cover PXC 8.0 under the operator, and how long will new operator releases ship PXC 8.0 images?

Steps to Reproduce:

Not applicable. This is a planning question, not a failure. The planned path is: operator 1.15 → 1.16.1 → 1.17.0 on OpenShift 4.14, then a new PXC 8.4 cluster restored from a backup of the 8.0 cluster.

Version:

  • OpenShift 4.14 (Kubernetes 1.27)
  • Percona Operator for MySQL based on PXC 1.15.0, installed cluster-wide through OLM (certified bundle)
  • PXC 8.0.36, HAProxy

Logs:

Not applicable.

Thanks,
Jin