Hello airbyte experts, I am exploring airbyte and wanted to install it on EKS. I followed the instructions provided here: https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm But a default installation (without any values.yaml) fails with the error message: failed pre-install: timed out waiting for the condition INSTALLATION FAILED I know I am missing something, could you please guide me?

hey @Santhosh Swaminathan do you mind editing your message and cutting the console output and pasting it here in 🧵 ? it helps keep the channel a little cleaner

Here is the console output: Here is the debug console output airbyte % helm install sandbox-airbyte2 airbyte/airbyte --debug install.go192 [debug] Original chart version: “” install.go209 [debug] CHART PATH: /Users/…/Library/Caches/helm/repository/airbyte-0.43.6.tgz client.go310 [debug] Starting delete for “airbyte-admin” ServiceAccount client.go339 [debug] serviceaccounts “airbyte-admin” not found client.go128 [debug] creating 1 resource(s) client.go310 [debug] Starting delete for “airbyte-db” StatefulSet client.go339 [debug] statefulsets.apps “airbyte-db” not found client.go128 [debug] creating 1 resource(s) client.go310 [debug] Starting delete for “airbyte-db-svc” Service client.go339 [debug] services “airbyte-db-svc” not found client.go128 [debug] creating 1 resource(s) client.go310 [debug] Starting delete for “airbyte-minio” StatefulSet client.go339 [debug] statefulsets.apps “airbyte-minio” not found client.go128 [debug] creating 1 resource(s) client.go310 [debug] Starting delete for “airbyte-minio-svc” Service client.go339 [debug] services “airbyte-minio-svc” not found client.go128 [debug] creating 1 resource(s) client.go310 [debug] Starting delete for “sandbox-airbyte2-airbyte-env” ConfigMap client.go339 [debug] configmaps “sandbox-airbyte2-airbyte-env” not found client.go128 [debug] creating 1 resource(s) client.go310 [debug] Starting delete for “sandbox-airbyte2-airbyte-secrets” Secret client.go339 [debug] secrets “sandbox-airbyte2-airbyte-secrets” not found client.go128 [debug] creating 1 resource(s) client.go310 [debug] Starting delete for “sandbox-airbyte2-airbyte-bootloader” Pod client.go339 [debug] pods “sandbox-airbyte2-airbyte-bootloader” not found client.go128 [debug] creating 1 resource(s) client.go540 [debug] Watching for changes to Pod sandbox-airbyte2-airbyte-bootloader with timeout of 5m0s client.go568 [debug] Add/Modify event for sandbox-airbyte2-airbyte-bootloader: ADDED client.go627 [debug] Pod sandbox-airbyte2-airbyte-bootloader pending client.go568 [debug] Add/Modify event for sandbox-airbyte2-airbyte-bootloader: MODIFIED client.go627 [debug] Pod sandbox-airbyte2-airbyte-bootloader pending client.go568 [debug] Add/Modify event for sandbox-airbyte2-airbyte-bootloader: MODIFIED client.go629 [debug] Pod sandbox-airbyte2-airbyte-bootloader running Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition helm.go84 [debug] failed pre-install: timed out waiting for the condition INSTALLATION FAILED main.newInstallCmd.func2 helm.sh/helm/v3/cmd/helm/install.go:141 github.com/spf13/cobra.(*Command).execute github.com/spf13/cobra@v1.5.0/command.go:872 github.com/spf13/cobra.(*Command).ExecuteC github.com/spf13/cobra@v1.5.0/command.go:990 github.com/spf13/cobra.(*Command).Execute github.com/spf13/cobra@v1.5.0/command.go:918 main.main helm.sh/helm/v3/cmd/helm/helm.go:83 runtime.main runtime/proc.go:250 runtime.goexit runtime/asm_arm64.s:1172 ------------------------------------------------------------------------------------------- Get pods returns this: airbyte % kubectl get pods NAME READY STATUS RESTARTS AGE airbyte-db-0 0/1 Pending 0 5m29s airbyte-minio-0 0/1 Pending 0 5m29s sandbox-airbyte2-airbyte-bootloader 1/1 Running 0 5m28s --------------------------------------------------------------------------------------------- get events returns this: kubectl get events --sort-by=‘{.lastTimestamp}’ LAST SEEN TYPE REASON OBJECT MESSAGE 58s Warning FailedScheduling pod/airbyte-db-0 running PreBind plugin “VolumeBinding”: binding volumes: timed out waiting for the condition 10m Normal SuccessfulCreate statefulset/airbyte-db create Claim airbyte-volume-db-airbyte-db-0 Pod airbyte-db-0 in StatefulSet airbyte-db success 10m Normal SuccessfulCreate statefulset/airbyte-db create Pod airbyte-db-0 in StatefulSet airbyte-db successful 57s Warning FailedScheduling pod/airbyte-minio-0 running PreBind plugin “VolumeBinding”: binding volumes: timed out waiting for the condition 10m Normal WaitForFirstConsumer persistentvolumeclaim/airbyte-minio-pv-claim-airbyte-minio-0 waiting for first consumer to be created before binding 50s Normal ExternalProvisioning persistentvolumeclaim/airbyte-minio-pv-claim-airbyte-minio-0 waiting for a volume to be created, either by external provisioner “ebs.csi.aws.com” or manually created by system administrator 10m Normal SuccessfulCreate statefulset/airbyte-minio create Claim airbyte-minio-pv-claim-airbyte-minio-0 Pod airbyte-minio-0 in StatefulSet airbyte-minio success 10m Normal SuccessfulCreate statefulset/airbyte-minio create Pod airbyte-minio-0 in StatefulSet airbyte-minio successful 10m Normal WaitForFirstConsumer persistentvolumeclaim/airbyte-volume-db-airbyte-db-0 waiting for first consumer to be created before binding 50s Normal ExternalProvisioning persistentvolumeclaim/airbyte-volume-db-airbyte-db-0 waiting for a volume to be created, either by external provisioner “ebs.csi.aws.com” or manually created by system administrator 14m Normal Starting node/ip-10-100-23-39.ec2.internal Starting kubelet. 14m Warning InvalidDiskCapacity node/ip-10-100-23-39.ec2.internal invalid capacity 0 on image filesystem 14m Normal NodeHasSufficientMemory node/ip-10-100-23-39.ec2.internal Node ip-10-100-23-39.ec2.internal status is now: NodeHasSufficientMemory 14m Normal NodeHasNoDiskPressure node/ip-10-100-23-39.ec2.internal Node ip-10-100-23-39.ec2.internal status is now: NodeHasNoDiskPressure 14m Normal NodeHasSufficientPID node/ip-10-100-23-39.ec2.internal Node ip-10-100-23-39.ec2.internal status is now: NodeHasSufficientPID 14m Normal NodeAllocatableEnforced node/ip-10-100-23-39.ec2.internal Updated Node Allocatable limit across pods 14m Normal RegisteredNode node/ip-10-100-23-39.ec2.internal Node ip-10-100-23-39.ec2.internal event: Registered Node ip-10-100-23-39.ec2.internal in Controller 14m Normal Starting node/ip-10-100-23-39.ec2.internal 14m Normal NodeReady node/ip-10-100-23-39.ec2.internal Node ip-10-100-23-39.ec2.internal status is now: NodeReady 14m Normal Starting node/ip-10-100-24-163.ec2.internal Starting kubelet. 14m Warning InvalidDiskCapacity node/ip-10-100-24-163.ec2.internal invalid capacity 0 on image filesystem 14m Normal NodeHasSufficientMemory node/ip-10-100-24-163.ec2.internal Node ip-10-100-24-163.ec2.internal status is now: NodeHasSufficientMemory 14m Normal NodeHasNoDiskPressure node/ip-10-100-24-163.ec2.internal Node ip-10-100-24-163.ec2.internal status is now: NodeHasNoDiskPressure 14m Normal NodeHasSufficientPID node/ip-10-100-24-163.ec2.internal Node ip-10-100-24-163.ec2.internal status is now: NodeHasSufficientPID 14m Normal NodeAllocatableEnforced node/ip-10-100-24-163.ec2.internal Updated Node Allocatable limit across pods 14m Normal RegisteredNode node/ip-10-100-24-163.ec2.internal Node ip-10-100-24-163.ec2.internal event: Registered Node ip-10-100-24-163.ec2.internal in Controller 14m Normal Starting node/ip-10-100-24-163.ec2.internal 14m Normal NodeReady node/ip-10-100-24-163.ec2.internal Node ip-10-100-24-163.ec2.internal status is now: NodeReady 10m Normal Scheduled pod/sandbox-airbyte2-airbyte-bootloader Successfully assigned default/sandbox-airbyte2-airbyte-bootloader to ip-10-100-23-39.ec2.internal 10m Normal Pulling pod/sandbox-airbyte2-airbyte-bootloader Pulling image “airbyte/bootloader:0.40.25" 10m Normal Pulled pod/sandbox-airbyte2-airbyte-bootloader Successfully pulled image “airbyte/bootloader:0.40.25” in 6.825273157s 10m Normal Created pod/sandbox-airbyte2-airbyte-bootloader Created container airbyte-bootloader-container 10m Normal Started pod/sandbox-airbyte2-airbyte-bootloader Started container airbyte-bootloader-container ------------------------------------------------------------------------------------------------------------------

@Santhosh Swaminathan i also found this it looks like there might not be a fix for your current bug

@Santhosh Swaminathan of Course, I used that documentation https://docs.airbyte.com/deploying-airbyte/on-kubernetes

Thanks @Omar Mayar. Is the issue specific to the helm chart? or is it specific to EKS? Looks like @Carlos Andres Aguirre Arias used

kubectl apply'

and still facing issue. if a resolution for that is available then that should work too.

I’m not sure, hopefully it gets triaged you’ll know the root cause. One option is to see if you can up your timeouts from 5m to see if the bootloader just needs more time (or see if you get a different output when you up the time to see if you get a more helpful error statement)

will do. Thanks!

you may want to share your yaml here, it’s possible that you need to update your configs to increase mem and storage

Hi @Omar Mayar - It turns out it is related to the Persistent Volume claim on the EKS cluster. I came across this stack overflow link: https://stackoverflow.com/questions/73871493/error-while-installing-mongodb-in-aws-eks-cluster-running-prebind-plugin-volu which describes a similar issue but for mongo db. I followed the steps and was able to get past this issue. Thanks for your help.

nice! you may want to update issue 14463 with this information to help others out