Hello, I'm trying to deploy airbyte in AWS EKS. However, I got the error below.

helm install --values /Users/bagelcode/Workspace/deploy-core-eks/values/airbyte.dev.yaml airbyte-dev-adhoc airbyte/airbyte --debug                1 err | data-core-eks-dev kube | 11:58:31 AM
install.go:173: [debug] Original chart version: ""
install.go:190: [debug] CHART PATH: /Users/bagelcode/Library/Caches/helm/repository/airbyte-0.40.40.tgz

client.go:282: [debug] Starting delete for "airbyte-dev-admin" ServiceAccount
client.go:122: [debug] creating 1 resource(s)
client.go:282: [debug] Starting delete for "airbyte-dev-adhoc-airbyte-env" ConfigMap
client.go:311: [debug] configmaps "airbyte-dev-adhoc-airbyte-env" not found
client.go:122: [debug] creating 1 resource(s)
client.go:282: [debug] Starting delete for "airbyte-dev-adhoc-airbyte-secrets" Secret
client.go:311: [debug] secrets "airbyte-dev-adhoc-airbyte-secrets" not found
client.go:122: [debug] creating 1 resource(s)
client.go:282: [debug] Starting delete for "airbyte-dev-adhoc-airbyte-bootloader" Pod
client.go:311: [debug] pods "airbyte-dev-adhoc-airbyte-bootloader" not found
client.go:122: [debug] creating 1 resource(s)
client.go:491: [debug] Watching for changes to Pod airbyte-dev-adhoc-airbyte-bootloader with timeout of 5m0s
client.go:519: [debug] Add/Modify event for airbyte-dev-adhoc-airbyte-bootloader: ADDED
client.go:578: [debug] Pod airbyte-dev-adhoc-airbyte-bootloader pending
client.go:519: [debug] Add/Modify event for airbyte-dev-adhoc-airbyte-bootloader: MODIFIED
client.go:580: [debug] Pod airbyte-dev-adhoc-airbyte-bootloader running
Error: failed pre-install: timed out waiting for the condition
helm.go:81: [debug] failed pre-install: timed out waiting for the condition

I cannot figure out what is the problem. I found slack archive, which is the same as my problem but has no solution. Could you help me how troubleshoot this problem? https://airbytehq.slack.com/archives/C021JANJ6TY/p1665660532221119?thread_ts=1665656538.448909&cid=C021JANJ6TY

Hello Seowan Lee, it's been a while without an update from us. Are you still having problems or did you find a solution?