Allow unstucking an update

[tnozicka]

Is this a bug report or feature request?

• Feature Request

What should the feature do: Currently (and previously) the operator is always waiting for the StatefulSet to be fully rolled out before it triggers an update. But in case of a bug and getting a newer version of the operator, this requires manual action to unstuck. The "Waiting for StatefulSet rollout" in the code is intentional to make sure all of the nodes are up to date but maybe we could do better.

There is also the StatefulSet bug that prevent rolling back from a broken state (https://github.com/kubernetes/kubernetes/issues/67250) but we should at least move that down to the statefulset which may get fixed in the meantime.

What is use case behind this feature: Stability.

Additional Information:

[scylla-operator-bot[bot]]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[tnozicka]

/remove-lifecycle stale /triage accepted