Hi, we've updated signoz from version 0.64.x to 0.82.x in one go - we had no issues, everything went well, signoz works correctly. But I have a question: how to determine if clickhouse pod will be recreated? We did '`helm upgrade xxx --version=<version number>`' command for every version (both major and minor to be sure every database migration and stuff executed correctly, minus versions that were suggested to skip due to issues), we didn't jump straight to version 0.82.x. And during all those upgrades clickhouse pod recreated one time when we updated 0.70.0 to 0.70.1 (chart 0.68.0 to 0.68.1). I don't see anything related in changelog https://github.com/SigNoz/charts/compare/signoz-0.68.0...signoz-0.68.1 or https://github.com/SigNoz/signoz/compare/v0.70.0...v0.70.1 that would straight suggest that clickhouse will be recreated (like "bump clickhouse to xxxx"). The pods aren't being recreated during helm upgrade process, the helm command shows:

Release "my-release" has been upgraded. Happy Helming!

(...) and it took about 5-6 minutes before the clickhouse pod went into

Terminating

and got recreated while the whole signoz deployment was in

Deployed

state and every resource

Complete

or

Running

. It's not a big issue, but when upgrading through multiple versions in one run it might end up trying to upgrade to the next version BEFORE the clickhouse pod recreated. It didn't happen to us, as right before the next helm upgrade command was executed we noticed that clickhouse pod went into

Terminating

state and got recreated, so we stopped and waited. But this extends the whole upgrade process, as we had to wait ~10 mins to be sure that every signoz resource is ready for next upgrade. We use the provided clickhouse in version 24.1.2-alpine