Hi, I am installing the latest airflow on

Kubernetes

following instructions at https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm. Am getting a timeout in the

pod/test-airbyte-bootloader

. Here is the output of

kubectl get all -n airbyte

$ kubectl get all -n airbyte
NAME                          READY   STATUS    RESTARTS   AGE
pod/airbyte-db-0              0/1     Pending   0          6m29s
pod/airbyte-minio-0           0/1     Pending   0          6m29s
pod/test-airbyte-bootloader   0/1     Error     0          6m28s

NAME                        TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
service/airbyte-db-svc      ClusterIP   10.100.198.153   <none>        5432/TCP   6m29s
service/airbyte-minio-svc   ClusterIP   10.100.148.255   <none>        9000/TCP   6m29s

NAME                             READY   AGE
statefulset.apps/airbyte-db      0/1     6m30s
statefulset.apps/airbyte-minio   0/1     6m30s

Does this mean, somehow, that I need to configure the

db

and

minio

? The instructions don't explain how those need to be configured. Here is the output of helm:

$ helm install test airbyte/airbyte -n airbyte --debug 2>&1 | tee /tmp/log.txt
install.go:200: [debug] Original chart version: ""
install.go:217: [debug] CHART PATH: /home/andrei/.cache/helm/repository/airbyte-0.46.0.tgz

client.go:478: [debug] Starting delete for "airbyte-admin" ServiceAccount
client.go:482: [debug] Ignoring delete failure for "airbyte-admin" /v1, Kind=ServiceAccount: serviceaccounts "airbyte-admin" not found
client.go:134: [debug] creating 1 resource(s)
client.go:478: [debug] Starting delete for "airbyte-db" StatefulSet
client.go:482: [debug] Ignoring delete failure for "airbyte-db" apps/v1, Kind=StatefulSet: statefulsets.apps "airbyte-db" not found
client.go:134: [debug] creating 1 resource(s)
client.go:478: [debug] Starting delete for "airbyte-db-svc" Service
client.go:482: [debug] Ignoring delete failure for "airbyte-db-svc" /v1, Kind=Service: services "airbyte-db-svc" not found
client.go:134: [debug] creating 1 resource(s)
client.go:478: [debug] Starting delete for "airbyte-minio" StatefulSet
client.go:482: [debug] Ignoring delete failure for "airbyte-minio" apps/v1, Kind=StatefulSet: statefulsets.apps "airbyte-minio" not found
client.go:134: [debug] creating 1 resource(s)
client.go:478: [debug] Starting delete for "airbyte-minio-svc" Service
client.go:482: [debug] Ignoring delete failure for "airbyte-minio-svc" /v1, Kind=Service: services "airbyte-minio-svc" not found
client.go:134: [debug] creating 1 resource(s)
client.go:478: [debug] Starting delete for "test-airbyte-env" ConfigMap
client.go:482: [debug] Ignoring delete failure for "test-airbyte-env" /v1, Kind=ConfigMap: configmaps "test-airbyte-env" not found
client.go:134: [debug] creating 1 resource(s)
client.go:478: [debug] Starting delete for "test-airbyte-secrets" Secret
client.go:482: [debug] Ignoring delete failure for "test-airbyte-secrets" /v1, Kind=Secret: secrets "test-airbyte-secrets" not found
client.go:134: [debug] creating 1 resource(s)
client.go:478: [debug] Starting delete for "test-airbyte-bootloader" Pod
client.go:482: [debug] Ignoring delete failure for "test-airbyte-bootloader" /v1, Kind=Pod: pods "test-airbyte-bootloader" not found
client.go:134: [debug] creating 1 resource(s)
client.go:706: [debug] Watching for changes to Pod test-airbyte-bootloader with timeout of 5m0s
client.go:734: [debug] Add/Modify event for test-airbyte-bootloader: ADDED
client.go:793: [debug] Pod test-airbyte-bootloader pending
client.go:734: [debug] Add/Modify event for test-airbyte-bootloader: MODIFIED
client.go:793: [debug] Pod test-airbyte-bootloader pending
client.go:734: [debug] Add/Modify event for test-airbyte-bootloader: MODIFIED
client.go:795: [debug] Pod test-airbyte-bootloader running
Error: INSTALLATION FAILED: failed pre-install: 1 error occurred:
	* timed out waiting for the condition


helm.go:84: [debug] failed pre-install: 1 error occurred:
	* timed out waiting for the condition


INSTALLATION FAILED
main.newInstallCmd.func2
	<http://helm.sh/helm/v3/cmd/helm/install.go:147|helm.sh/helm/v3/cmd/helm/install.go:147>
<http://github.com/spf13/cobra.(*Command).execute|github.com/spf13/cobra.(*Command).execute>
	<http://github.com/spf13/cobra@v1.6.1/command.go:916|github.com/spf13/cobra@v1.6.1/command.go:916>
<http://github.com/spf13/cobra.(*Command).ExecuteC|github.com/spf13/cobra.(*Command).ExecuteC>
	<http://github.com/spf13/cobra@v1.6.1/command.go:1044|github.com/spf13/cobra@v1.6.1/command.go:1044>
<http://github.com/spf13/cobra.(*Command).Execute|github.com/spf13/cobra.(*Command).Execute>
	<http://github.com/spf13/cobra@v1.6.1/command.go:968|github.com/spf13/cobra@v1.6.1/command.go:968>
main.main
	<http://helm.sh/helm/v3/cmd/helm/helm.go:83|helm.sh/helm/v3/cmd/helm/helm.go:83>
runtime.main
	runtime/proc.go:250
runtime.goexit
	runtime/asm_amd64.s:1598

A message from kapa.ai

Ok. Problem was - persistent volumes are not configured by default in AWS EKS. After running

eksctl create cluster --name my-cluster --region region-code

you need to do the steps below: • Creating an IAM OIDC provider for your cluster • Creating the Amazon EBS CSI driver IAM role • Deploy a sample application and verify that the CSI driver is working Then, create a namespace and install AIrbyte:

kubectl create namespace airbyte
helm install airbyte airbyte/airbyte --version 0.45.50 --namespace airbyte --debug

@Andrei Radulescu-Banu thank you for writing this up! It saved me a lot of headaches.. One addition to the above: after you create the EBS CSI driver IAM role, you also need to add the EBS CSI driver add-on to the EKS cluster as written up here.