Story: As a Quay customer using the Operator in version 3.3 I want to be able to upgrade to the Quay Operator 3.6 release directly to transition to the new Quay Operator logic without regressions in Route handling, rollout speed, stability and reconciliation robustness.
Background: Due to several refactorings and some churn caused by backwards incompatible changes of k8s library dependencies it is not practical to backport all Operator improvements all the way back to 3.4 or 3.5. Hence we need to enable customers to jump directly to 3.6 in order for them to avoid running 3.4 or 3.6 releases in which several undesireable behaviors of the Operator are present.
- the migration logic from 3.3 Operators is still present in 3.6
- the OLM update graph allows direct update from 3.3 to 3.6
- the Quay version can be updated directly from 3.3 to 3.6
- Edge Route setups in the old Operator will transition to Edge Route setups as proposed in