This causes the operator to end up in an infinite MigrationsInProgress state where it waits for the condition that never comes. This is primarily a problem on operator and Quay updates where new rollout is blocked. The only solution is to manually scale down main Quay app deployment and then manually scale up the upgrade deployment. At this point, the operator gets the desired signal from the upgrade pod, reconciles configuration, updates what needs to be updated and then leaves the CR in the Available state.