SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

SigNoz Community

I am trying to deploy Signoz onto an AWS EKS cluster but having a rough time of it.  The pods will not start and are stuck in a status of pending due to PVC problems:
Warning FailedScheduling 4m52s (x16 over 80m) default-scheduler 0/2 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling

I can successfully deploy other apps onto this same cluster with no issue.

I am not sure if the problem is with the cluster itself or the helm charts.  I have added overrides to values.yaml, i have also tried no overrides in values.yaml at all, with no success.  What should be in my values.yaml to get this deployed properly? Or could it be the cluster itself?
I realize this might be a complicated question, i can provide any more info needed.

Hey <@U090C3L3KFH> Are you using the Custom Class according to your Cloud Provider?

i got the storage figured out finally, ultimately it was a combination of problems with pod identity associations

but yes i created a storage class, added that class name to my values.yaml along with installCustomStorageClass true