Hi Team, We are trying to deploy signoz on an EKS cluster on AWS. We followed the steps mentioned here - https://signoz.io/docs/install/kubernetes/aws/ But otel-collector, otel-collector-metrics and query-service containers are stuck in CrashLoopBackOff state And we are getting below errors - ERROR clickhouseReader/reader.go:113 failed to initialize ClickHouse: error connecting to primary db: code: 516, message: admin: Authentication failed: password is incorrect or there is no user with such name Can anyone please help, if this is a version issue, and provide version numbers to use?

hey @Amul P Kesrani Which version of SigNoz are you trying to install and how much resources have you allocated?

Hi @Amul P Kesrani 👋 That usually happens due to clickhouse IP whitelisting. Could you please share the output of the following?

kubectl -n platform get pods -o=wide

Hi @Pranay Resources are on-demand, and we are using below versions - --set frontend.image.tag="0.11.0" \ --set queryService.image.tag="0.11.0" \ --set otelCollector.image.tag="0.55.0" \ --set otelCollectorMetrics.image.tag="0.55.0"

signoz/clickhouse

chart by default allows following private IPs:

- "10.0.0.0/8"
    - "172.16.0.0/12"
    - "192.168.0.0/16"

How can I whitelist my ip range?

You can either whitelist IP range

100.64.0.0/16

in

clickhouse.allowedNetworkIps

https://github.com/SigNoz/charts/blob/main/charts/signoz/values.yaml#L117-L120

I am trying to reinstall, after updating the allowedNetworkIp in override-values.yaml

@Amul P Kesrani can you share override-values.yaml?

@Amul P Kesrani yeah, looks good to me!

The pods are up now, and I am able to access the signoz frontend, Thank you @Prashant Shahi

That's great to hear 🎉

No, we are using terraform for the same

You are second person this week who had application deployed at 100.64.X.X