Setting the ``updateStrategy: OnDelete`` didn't work if was not specified from scratch in CR
General
Escalation
General
Escalation
Description
In CLOUD-520 we've faced an error in case of switching from RollingUpgrade to OnDelete strategy. It happens when CR does not contain any strategy specified and Kubernetes sets it's default value (RollingUpgrade) with partitioning for StatefulSet. Operators' logic does not take into accout that partition section should be wiped out and leaves it as is which leads to an error.
In CLOUD-520 we've faced an error in case of switching from RollingUpgrade to OnDelete strategy. It happens when CR does not contain any strategy specified and Kubernetes sets it's default value (RollingUpgrade) with partitioning for StatefulSet. Operators' logic does not take into accout that partition section should be wiped out and leaves it as is which leads to an error.