Hello Signoz people I’m having issues setting up cold storage It’s not really clear what should be put in these variables in the following section: —— clickhouse: coldStorage: enabled: true defaultKeepFreeSpaceBytes: "1073741824" type: gcs endpoint: "" accessKey: "???" secretAccess: “???” —— For the context we’re on GCP and Kubernetes and I tried to put k8s secret name and secret’s key name there but that didn’t work. The secret contains bucket json key. Any suggestions?

Hey @Roman Levytskyi PTAL: https://signoz.io/docs/userguide/retention-period/#configuring-cold-storage---google-cloud-storage-gcs

@Nagesh Bansal i did exactly like that, (check snippet above), still I’m not sure folder is being written to, although no free space left. I checked the docs section for kubernetes and did exactly according to it

@Roman Levytskyi the type should be

gcs

if you're going for gcs the helm charts ensure ClickHouse is compatible with GCS can you share the logs from the clickhouse pod

clickhouse.txt

Please ensure that both keys are of following format:

access_key_id: SERVICE ACCOUNT HMAC KEY
secret_access_key: SERVICE ACCOUNT HMAC SECRET

can you please elaborate more @Nagesh Bansal? i currently have it like this:

accessKey: "service-account-key"
secretAccess: "signoz-storage-secret"

PTAL: https://cloud.google.com/storage/docs/authentication/hmackeys

thanks @Nagesh Bansal is it possible to use

valueFrom

on both of those keys?

Hey @Roman Levytskyi, let me check what can we do here

yes, it’s working fine, although retrieving traces/logs got slower now, the issue is that the secrets are right in the manifest, which is unsafe and they should stay in k8s secrets