This message was deleted.

Hey @Hima Vyas! In case of the latest SigNoz version, we have couple of things changed. You could run the following for AWS:

helm -n platform upgrade my-release signoz/signoz \
   --set clickhouse.installCustomStorageClass=true \
   --set clickhouse.cloud=aws \
   --set clickhouse.persistence.size=25Gi \
   --set clickhouse.persistence.storageClass=gp2-resizable

In case of Google Cloud: • set

clickhouse.cloud

to

gcp

• set

clickhouse.persistence.storageClass

to

gce-resizable

Will running this command be sufficient or any restart is also required?

@Hima Vyas I suppose you had started the SigNoz cluster with default configurations. That would be require little more steps to not lose any data. Since SigNoz picks the default StorageClass which is usually not expandable unless specified otherwise. 1. In case of AWS, you would have to edit

gp2

storage class.

$ kubectl edit sc -n platform gp2

And include the following:

allowVolumeExpansion: true

2. Run helm upgrade command:

helm -n platform upgrade my-release signoz/signoz \
   --set clickhouse.persistence.size=25Gi

3. (Optional) After the size changes reflect in few minutes, you could edit the default storage class

gp2

back to its previous state.

Thanks Prashant! will follow