The motivation for this backport stems from https://github.com/planetscale/vitess-operator/issues/608, as explained by @bluecrabs007, the goal of the original PR is to support two versions of MySQL in the cluster instead of using the same one everywhere, this is very useful as we were deprecating MySQL 5.7. However, we deprecated MySQL 5.7 in v18.0.0 (equivalent of v2.11 in vtop) and removed it entirely from the code base in v19.0.0 (equivalent v2.12 in vtop).
We want to backport this to v2.11 so users can use the feature, and thus migrate more easily, on a version of Vitess where MySQL 5.7 is still supported.
This is a backport of https://github.com/planetscale/vitess-operator/pull/524 into
release-2.11.The motivation for this backport stems from https://github.com/planetscale/vitess-operator/issues/608, as explained by @bluecrabs007, the goal of the original PR is to support two versions of MySQL in the cluster instead of using the same one everywhere, this is very useful as we were deprecating MySQL 5.7. However, we deprecated MySQL 5.7 in v18.0.0 (equivalent of v2.11 in vtop) and removed it entirely from the code base in v19.0.0 (equivalent v2.12 in vtop).
We want to backport this to
v2.11so users can use the feature, and thus migrate more easily, on a version of Vitess where MySQL 5.7 is still supported.This PR is part of https://github.com/planetscale/vitess-operator/issues/608. It fixes the
Issue 2described.