Unable to customize StatefulSet updateStrategy

Hello,

We are using ClickHouse Operator version 0.25.0 and noticed that the StatefulSet update strategy is hardcoded to RollingUpdate, despite attempts to override it via the podTemplates spec:

podTemplates:
  - name: clickhouse-with-volume-template
    generateName: "chi-{cluster}-{host}"
    spec:
      updateStrategy:
        type: OnDelete

Our use case requires OnDelete to avoid pod reconcile triggered by minor config changes (e.g., max_concurrent_queries; when changed under spec > configuration > settings.

While configurationRestartPolicy works as expected to prevent ClickHouse restarts, the StatefulSet reconcile still leads to full pod termination and recreation due to the update strategy.

We confirmed in the code (stateful-set.go) that the updateStrategy is explicitly set to RollingUpdate, ignoring our podTemplates settings.

Additional notes:
Operator logs show reconciles triggered by label/object version changes, causing pod recreation.

Request:

Support for customizing the StatefulSet updateStrategy (e.g., allowing OnDelete).

Thanks for your help!

Start at pkg/model/common/creator/stateful-set.go around line 57 and trace how podTemplates settings are handled when the StatefulSet is created. The work is done when a podTemplates updateStrategy such as OnDelete is honored instead of being overridden by RollingUpdate; the payload names no test to run.