Install airbyte in kubenates with helm chart

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: EKS on AWS
  • Deployment: kubenates using helm
  • Airbyte Version: What version are you using now?
  • Step:
  1. cd airbyte/charts/airbyte
  2. ./ci.sh install
    I found the following error

history.go:56: [debug] getting history for release airbyte
Release “airbyte” does not exist. Installing it now.
install.go:178: [debug] Original chart version: “”
install.go:195: [debug] CHART PATH: /Users/airbyte/charts/airbyte

client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for “airbyte-admin” ServiceAccount
client.go:328: [debug] serviceaccounts “airbyte-admin” not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for “airbyte-env” ConfigMap
client.go:328: [debug] configmaps “airbyte-env” not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for “airbyte-postgresql” Secret
client.go:328: [debug] secrets “airbyte-postgresql” not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for “airbyte-postgresql” Service
client.go:328: [debug] services “airbyte-postgresql” not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for “airbyte-postgresql” StatefulSet
client.go:328: [debug] statefulsets.apps “airbyte-postgresql” not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for “airbyte-postgresql-headless” Service
client.go:328: [debug] services “airbyte-postgresql-headless” not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for “airbyte-secrets” Secret
client.go:328: [debug] secrets “airbyte-secrets” not found
client.go:128: [debug] creating 1 resource(s)
client.go:299: [debug] Starting delete for “airbyte-bootloader” Pod
client.go:328: [debug] pods “airbyte-bootloader” not found
client.go:128: [debug] creating 1 resource(s)
client.go:529: [debug] Watching for changes to Pod airbyte-bootloader with timeout of 10m0s
client.go:557: [debug] Add/Modify event for airbyte-bootloader: ADDED
client.go:616: [debug] Pod airbyte-bootloader pending
Error: failed pre-install: timed out waiting for the condition
helm.go:84: [debug] failed pre-install: timed out waiting for the condition

And airbyte-bootloader and airbyte-postgresql-0 are still pending.
Is this the right way to install it with helm chart?

Hey @zigbang-yeezy,
The right way to deploy Airbyte on Kubernetes with the Helm chart of our repo is to run Helm commands after installing the helm CLI.
Something like :

helm install [app-name] [chart] --values [yaml-file/url]
1 Like

Thanks @alafanechere. Can you explain what the ci.sh is for? It’s presence is confusing if we’re not supposed to use it

The ci.sh is used in our continuous integration platform to run test on the helm chart. You can try to run ./ci.sh install that is wrapping the helm install with some specific options we use to run in the CI, it’s running:

    helm upgrade --install \ --create-namespace \ --namespace "${NAMESPACE}" \ --debug \ --wait \ --timeout "${INSTALL_TIMEOUT}" \ "${RELEASE_NAME}" .