Deploy with helm chart on AWS

[bartoszkosciug]

Bug description

Cant run the signoz on the AWS, the problem is that chi-signoz-cluster dont want to run:

Expected behavior

The expected behavior is that helm chart is deployed with success - all pods are running.

How to reproduce

1. Create override-values.yaml file clickhouse: cloud: aws installCustomStorageClass: true persistence: storageClass: gp2-resizable
2. helm repo add signoz https://charts.signoz.io
3. kubectl create ns platform
4. helm --namespace platform install my-release signoz/signoz -f override-values.yaml

Version information

N/A

Additional context

N/A

Thank you for your bug report – we love squashing them!

[welcome[bot]]

Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.

[AkshayAwate]

can you provide logs of pod kubectl logs <chi-pod> or please paste the output of kubectl describe pod <chi-pod-name> ? @bartoszkosciug

[prashant-shahi]

@AkshayAwate Thanks for the message in the thread. It turns out that I missed out on it.

@bartoszkosciug we have updated quite a lot of things in charts recently. As Akshay stated logs and pod state would be very helpful. But yeah, ideally chi-pod should be ready in few minutes followed by other pods being ready.

[prashant-shahi]

Not able to replicate the issue in EKS with K8s version <= 0.22.

@bartoszkosciug Closing this issue as we are unable to reproduce this. Feel free to re-open if you could share the steps to reproduce the same using latest helm chart.