Trying to install Airbyte on Kubernetes EKS with helm and I'm getting a timeout, so I increased the timeout but it seems to still be stuck. The db and minio pods seem to be stuck in pending mode. Any ideas?

airbyte % kubectl get pods    
NAME                             READY   STATUS    RESTARTS   AGE
0.40.25-airbyte-bootloader       1/1     Running   0          57m
0.43.6-airbyte-bootloader        1/1     Running   0          33m
airbyte-db-0                     0/1     Pending   0          17m
airbyte-minio-0                  0/1     Pending   0          17m
hmd-airbyte-airbyte-bootloader   1/1     Running   0          17m

Can you run describe on the pending pods? It should show which event it is waiting for

@Marcelo Pio de Castro ok, I did that and it says this warning: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 9m23s (x91 over 15h) default-scheduler running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition

So, it seems it is not being able to mount the volumes that it tries to create for the airbyte-db and minio

Would this be a persistent volume? If so, I did a list and there's nothing.

Try to list volume claims instead, since volume claim is created first and then it requests volume to be created

Thanks @Kyryl Skobylko, I listed out those and did a describe and see this:`waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator`

Do you have permission to create a EBS volume?