Apache Pinot

```test                pinot-broker-0                                   0/1     CrashLoopBackOff   5 (10s ago)   3m46s
test                pinot-controller-0                               0/1     Pending            0             3m46s
test                pinot-server-0                                   0/1     Pending            0             3m46s
test                pinot-zookeeper-0                                1/1     Running            0             3m46s```

broker error log.txt

I have added storageclass to gp2 and changed resources to `{} in values`

The controller sets up the cluster and creates nodes in the zookeeper. Other components including brokers are failing since the controller is not up yet. You can describe the controller pod to see in events why it is in a pending state. Most likely you don't have nodes in the eks cluster that can run controller pods. At least that has been my experience with this state. Good luck!

Thankyou <@U013436PDRQ> I was only checking broker logs not the other pod logs since those are pending. But checking controller logs gave me the root cause of the issue. The storage class and pvc's. I followed below steps and fixed the issue.

```Controller pod events:
Events:
  Type     Reason             Age   From                Message
  ----     ------             ----  ----                -------
  Warning  FailedScheduling   55s   default-scheduler   0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
  Normal   NotTriggerScaleUp  51s   cluster-autoscaler  pod didn't trigger scale-up: 1 pod has unbound immediate PersistentVolumeClaims

step 1)
kubectl get pvc -n &lt;namespace&gt;
NAME                      STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
data-pinot-controller-0   Pending                                                                        gp3            42h
data-pinot-minion-0       Bound     pvc-fafd475e-697c-4922-b434-b0f25de9a674   4Gi        RWO            gp2            24h
data-pinot-server-0       Pending                                                                        gp3            42h
data-pinot-server-1       Pending                                                                        gp3            42h

step 2)
kubectl get pvc -n &lt;namespace&gt;

step 3)
kubectl delete pvc &lt;pvcname&gt; -n &lt;namespace&gt;

step 4)
Changed storage class to gp2

step 5)
redeployed the helm charts
kubectl get pods -n &lt;namespace&gt;
NAME                 READY   STATUS    RESTARTS      AGE
pinot-broker-0       1/1     Running   1 (12m ago)   12m
pinot-controller-0   1/1     Running   0             12m
pinot-server-0       1/1     Running   1 (12m ago)   12m
pinot-server-1       1/1     Running   0             12m
pinot-zookeeper-0    1/1     Running   0             12m```