Description
What happened?
I think the current behaviour and integration between DeletionMode and PodUpdateStrategy of the operator is confusing to users. For example if a user set DeletionMode to None the user would expect that the operator is not deleting any Pods but the operator will still be able to replace Pods e.g. triggered automatically or by changing a specific setting. I think the more consistent behaviour would be to prevent any deletion and replacements if the DeletionMode is set to None and only if the DeletionMode is different than None the operator will do replacements (but not honouring the actual DeletionMode for replacements).
This issue get's more interesting when we use the default for PodUpdateStrategy to replace the transaction system, because now the transaction system will be updated but the rest of the cluster won't.
What did you expect to happen?
I think we should implement the behaviour like I mentioned above and document the different interactions better.
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
No response