Deploying SigNoz with Kubernetes - Stuck in Pods
TLDR Dedy experienced issues while deploying SigNoz with Kubernetes, as the pods were stuck. Prashant identified missing CHI pods as the cause and suggested trying `helm upgrade`.
Prashant
Mon, 10 Apr 2023 11:21:10 UTCHi Dedy :wave: I see that there is no clickhouse instance (CHI) pods, which is causing it.
Prashant
Mon, 10 Apr 2023 11:24:33 UTCThis usually happens for following reasons: • setting `layout.shardCount` to `0` • insufficient resources in the K8s cluster • inappropriate cleanup of previous signoz chart release in the same namespace
Prashant
Mon, 10 Apr 2023 11:25:07 UTCcan you try `helm upgrade` command with your `override-values.yaml` once again?
SigNoz Community
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
View in App
Dedy
Mon, 10 Apr 2023 05:49:57 UTChi guys, i'm a new on signoz, i'm tried to deployed signoz but i got a stuck in pods, this is my pods stuck on the init. when i'm describe i got the error pvc, but when i'm check the pvc has been bound. can i got solution?, im tried deployed signoz using kubernetes.