kubectl get pods -n platform NAME ...
# support
s
kubectl get pods -n platform NAME READY STATUS RESTARTS AGE signoz-release-alertmanager-0 1/1 Running 0 5d23h signoz-release-clickhouse-operator-7648754fdf-pxtkz 2/2 Running 0 20m signoz-release-frontend-5d8d4bcf96-xcjhr 1/1 Running 0 5d23h signoz-release-frontend-76d7ff5895-kwpbx 0/1 Init:0/1 0 20m signoz-release-otel-collector-kbnvr 0/1 Init:0/1 0 20m signoz-release-otel-collector-metrics-57f4977457-xfh7h 0/1 Init:0/1 0 20m signoz-release-otel-collector-metrics-7df59bc9cd-hf4kq 1/1 Running 0 5d23h signoz-release-otel-collector-v97nc 0/1 Init:0/1 0 2m55s signoz-release-query-service-0 0/1 Init:0/1 0 20m signoz-release-zookeeper-0 1/1 Running 0 5d23h
f
It looks like pods in init stage are waiting for clickhouse db
s
But click house db should created automatically
f
Yeah operator creates db cluster but in your problem it seems like there is a configuration problem. Can you also provide your installation method?
In my company case we are using helm chart and when you uninstall signoz using helm, it mostly cant delete crds you need to clear them manually
s
Found the issue and pasted
In thread
It is looking for Service account which is not there