TLDR Sajid sought help with configuring SigNoz installation in an on-prem Kubernetes cluster with Ceph storage, but resolved the issue by making their desired storageClass the default.
I'm trying to install SigNoz in our on-prem Kubernetes cluster. We are using Ceph as storage and storage class is also created for the same. As per the documentation, we have to set `global.storageClass` configuration to desired storage class for our custom storage class. But I'm not sure where should I made this change. Also, if this change is required in value file, which command should I run to upgrade helm. Can someone pls help with the same?
Instead of updating global.storageClass, I've made my storageClass as default which I wanted to use and it fixed my issue.
Indexed 1061 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI