Error getting connection from data source hikaridatasource (hikaripool-1) -- During AWS EKS deployment

During the deployment on AWS EKS, few pods are running/ Pending but bootloader got errored out. First snapshot also have airbyte-db configuration.
I am not getting which configuration I should change?

Below is the error


  • Is this your first time deploying Airbyte?: Yes
  • Deployment: Kubernetes deployment
  • Airbyte Version: What version are you using now? using latest version till today
    pods getting created
  • Description:
    Airbyte-db pod status is Error and error is “error getting connection from data source hikaridatasource (hikaripool-1)”

Similar error as mentioned in thread Failed to connect to external postgres DB.
All pods are in same VPC under same cluster

All default setting is used except namespace in kustomization.yaml.

Hello @RahulPatel, could you tell me what connectors/versions you are using? I found an open issue that might be related, but need a few more details:

It’s not connector issue, I deployed Airbyte on AWS EKS. Deployment is completed but bootloader pods are not getting up. Bootloader service is not able to connect with airbyte-db.

I see! You’re not using helm, correct? Could you provide the full logs?

Hi @natalyjazzviolin ,
I work with Rahul and attached is what you asked for.

All Pods after deployment.

$ kubectl get pods -n ns-0026-idl | grep airbyte
airbyte-bootloader-796hf 0/1 Error 0 3m6s
airbyte-bootloader-wp6tx 0/1 Pending 0 32s
airbyte-db-596f7fdb48-ntvcw 0/1 Pending 0 3m8s
airbyte-minio-5f776f998c-xxl4x 0/1 Pending 0 3m8s
airbyte-pod-sweeper-78bfcbd996-5zl7r 1/1 Running 0 3m8s
airbyte-server-989b4dfc6-qfhdv 0/1 Pending 0 3m7s
airbyte-temporal-6686b8c895-m5fls 1/1 Running 0 3m7s
airbyte-webapp-58cb994996-jzpl5 1/1 Running 0 3m7s
airbyte-worker-7967b8954f-fvdvl 1/1 Running 0 3m7s
airbyte-bootloader-logs.log (4.8 KB)
AirByte-deployment steps and output.txt (1.3 KB)

Thanks, @suman9730! And to double check: you are not using helm?

Yes @natalyjazzviolin, we are not using helm.

Gotcha! This is redundant, but just in case - could you recheck the port the database is using? I’m looking further into this, and if we don’t find an evident solution today/tomorrow, I’ll escalate it to GitHub.

1 Like

We are using the default settings without any change. (See attached)
env.txt (2.4 KB)
secrets.txt (224 Bytes)

env.txt = .env
secrets.txt = .secrets

If you were using this doc for setting up the database, the port needs to be 3000 and not 5432:

We are using On Kubernetes (Beta) | Airbyte Documentation to deploy the default installation on AWS EKS.

Getting the same error, even after changing the port to 3000

@natalyjazzviolin Do you have any working template and setting which works for you on AWS EKS since default configs templates are not working.

@RahulPatel I’m looking into it, should have an update for you soon!