Operator cannot be upgraded from a previous version from operatorhub.io

[yersan]

We have been using the leader-for-life strategy to configure the leader election. With the latest Operator SDK upgrade, this strategy has become problematic when the Operator is being upgraded to a new version. The new release has to become the leader, however, the old version is not removed until the new one is available. That leads to the situation of a deadlock where the lock is never released waiting for the new version.

We have been using this strategy from the beginning, but it seems we have hit the problem only now after the SDK upgrade to 1.22.

The default strategy used by the Operator SDK is Leader with lease, so we could use such a strategy instead. This strategy could lead to a split-brain situation, so it must be evaluated more carefully before proceeding. Meanwhile, we can update the lock name so the leader election can succeed in the middle of an upgrade.

See k8s-operatorhub/community-operators#3934 as reference