Deploy EKS - failed pre-install: timed out waiting for the condition

Platform, Deploy & Infra Issues
,
1

→

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: AWS EKS
  • Memory / Disk: m5.4xlarge
  • Deployment: Kubernetes
  • Airbyte Version: What version are you using now? 0.40.17
  • Source name/version:
  • Destination name/version:
  • Step: The issue is happening during sync, creating the connection or a new source?
  • Description:
    I’m trying to deploy on EKS with default values (as in tutorial) but installation fails at bootloader
    –
    Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition
    helm.go:84: [debug] failed pre-install: timed out waiting for the condition
    INSTALLATION FAILED
    –
    how should I proceed?
3

Hi,

Thanks for the question. Can you post the logs? In addition: can you post the results of running:

  1. helm ls --namespace airbyte
  2. kubectl get pods -n airbyte
  3. kubectl -n airbyte get events --sort-by=‘{.lastTimestamp}’
4

kubectl logs airbyte-airbyte-bootloader -n airbyte
2022-11-10 00:01:55,387 main INFO Loading mask data from '/seed/specs_secrets_mask.yaml
2022-11-10 00:01:55 INFO i.a.c.EnvConfigs(getEnvOrDefault):1079 - Using default value for environment variable CONFIG_DATABASE_USER: ‘airbyte’
2022-11-10 00:01:55 INFO i.a.c.EnvConfigs(getEnvOrDefault):1079 - Using default value for environment variable CONFIG_DATABASE_PASSWORD: ‘*****’
2022-11-10 00:01:55 INFO i.a.c.EnvConfigs(getEnvOrDefault):1079 - Using default value for environment variable CONFIG_DATABASE_URL: ‘jdbc:postgresql://airbyte-db-svc:5432/db-airbyte’
2022-11-10 00:01:55 INFO c.z.h.HikariDataSource():80 - HikariPool-1 - Starting…
2022-11-10 00:01:55 INFO c.z.h.HikariDataSource():82 - HikariPool-1 - Start completed.
2022-11-10 00:01:55 INFO c.z.h.HikariDataSource():80 - HikariPool-2 - Starting…
2022-11-10 00:01:55 INFO c.z.h.HikariDataSource():82 - HikariPool-2 - Start completed.
2022-11-10 00:01:55 INFO i.a.c.EnvConfigs(getEnvOrDefault):1079 - Using default value for environment variable SECRET_PERSISTENCE: ‘TESTING_CONFIG_DB_TABLE’

helm ls --namespace airbyte
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
airbyte airbyte 1 2022-11-10 09:01:35.401011 +0900 KST failed airbyte-0.40.40 0.40.17

kubectl get pods -n airbyte
NAME READY STATUS RESTARTS AGE
airbyte-airbyte-bootloader 1/1 Running 0 6m51s
airbyte-db-0 0/1 Pending 0 6m51s
airbyte-minio-0 0/1 Pending 0 6m51s

kubectl -n airbyte get events --sort-by=‘{.lastTimestamp}’
LAST SEEN TYPE REASON OBJECT MESSAGE
7m26s Normal Scheduled pod/airbyte-airbyte-bootloader Successfully assigned airbyte/airbyte-airbyte-bootloader to ip-***.ap-northeast-2.compute.internal
7m25s Normal Pulling pod/airbyte-airbyte-bootloader Pulling image “airbyte/bootloader:0.40.17”
7m14s Normal Pulled pod/airbyte-airbyte-bootloader Successfully pulled image “airbyte/bootloader:0.40.17” in 10.556617709s
7m8s Normal Created pod/airbyte-airbyte-bootloader Created container airbyte-bootloader-container
7m8s Normal Started pod/airbyte-airbyte-bootloader Started container airbyte-bootloader-container
7m26s Normal SuccessfulCreate statefulset/airbyte-db create Claim airbyte-volume-db-airbyte-db-0 Pod airbyte-db-0 in StatefulSet airbyte-db success
7m26s Normal SuccessfulCreate statefulset/airbyte-db create Pod airbyte-db-0 in StatefulSet airbyte-db successful
7m26s Normal WaitForFirstConsumer persistentvolumeclaim/airbyte-minio-pv-claim-airbyte-minio-0 waiting for first consumer to be created before binding
112s 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
7m26s Normal SuccessfulCreate statefulset/airbyte-minio create Claim airbyte-minio-pv-claim-airbyte-minio-0 Pod airbyte-minio-0 in StatefulSet airbyte-minio success
7m26s Normal SuccessfulCreate statefulset/airbyte-minio create Pod airbyte-minio-0 in StatefulSet airbyte-minio successful
7m26s Normal WaitForFirstConsumer persistentvolumeclaim/airbyte-volume-db-airbyte-db-0 waiting for first consumer to be created before binding
112s 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

5

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