Configurable .spec.strategy for mongodb deployment?

[mxmCherry]

TL;DR: Can we have a configurable mongodb rollout strategy for clickstack chart?

---

Bumped into issue with clickstack chart upgrade:

• clickstack chart upgrade 1.1.0 -> 1.1.1
• mongodb image version changed (5.0.14 -> 5.0.32)
• Deployment tried to spin a new mongodb Pod
• that new Pod failed to start with DBPathInUse: Unable to lock the lock file: /data/db/mongod.lock (Resource temporarily unavailable). Another mongod instance is already running on the /data/db directory

My clickstack HelmRelease mostly relies on defaults (mongodb.enabled=true + mongodb.persistence.enabled=true), and persistence is desired.

I managed to get the chart updated by zero-scaling the mongodb Deployment first (kubectl scale --replicas=0 deployment/<clickstack-name>-mongodb -n <namespace>) and then triggering the chart upgrade.

Similar outcome could be achieved with .spec.strategy.type=Recreate.

But for now, mongodb Deployment neither forces Recreate strategy, nor allows to specify it: https://github.com/ClickHouse/ClickStack-helm-charts/blob/clickstack-1.1.1/charts/clickstack/templates/mongodb-deployment.yaml#L24-L88

I would be happy to set .Values.mongodb.strategy.type=Recreate.