Pedro Doria
05/29/2023, 12:43 PMBenjamin Groves
05/29/2023, 1:39 PMv0.45.22
and connect it to an external Postgres database using an existing kubernetes secret.
Here is my values.yaml
externalDatabase:
host: <http://prod-data-platform.cluster-cumb1b60veam.eu-west-1.rds.amazonaws.com|prod-data-platform.cluster-cumb1b60veam.eu-west-1.rds.amazonaws.com>
user: eterlast
existingSecret: data-platform-external-secret
existingSecretPasswordKey: DATABASE_PASSWORD
database: airbyte
port: 5432
postgresql:
enabled: false
However, when I deploy this, I am getting this error from the airbyte-bootloader
pod:
Error: couldn't find key DATABASE_PASSWORD in Secret data-platform/data-platform-external-secret
I have seen this issue discussed a few times in here, but regardless, it doesn't work for me. Does anyone have a concrete way of getting this to work?
Looking into the helm template for the secret.yaml on artifacthub.io, I noticed the the DATABASE_PASSWORD
secret is wrapped in an if statement
which blocks its creation:
{{ if eq .Values.externalDatabase.existingSecret "" -}}
DATABASE_PASSWORD: {{ .Values.externalDatabase.password | default .Values.postgresql.postgresqlPassword | quote }}
{{ end -}}
Octavia Squidington III
05/29/2023, 7:45 PMPedro Doria
05/29/2023, 11:12 PMQuang Dang Vu Nhat
05/30/2023, 3:29 AMgit pull origin master
(which I have used many times before)
but this time, when I boot up using /run-ab-platform.sh
, it returned with error
airbyte-bootloader exited with code 255
service βbootloaderβ didnβt complete successfully: exit 255Then I started again by pull a fresh airbyte repo to start, but still the same error occurs Anyone know about this issue ? Appreciate your help.
ratibor78
05/30/2023, 12:41 PMratibor78
05/30/2023, 12:42 PMratibor78
05/30/2023, 12:58 PMAnchit
05/30/2023, 6:37 PMJake Kagan
05/30/2023, 9:23 PM.env
do you just do compose down
?ratibor78
05/31/2023, 6:02 AMSrikanth Sudhindra
05/31/2023, 4:34 PMAurΓ©lien Tamisier
05/31/2023, 4:36 PMv0.40.29
on Kubernetes, using Helm charts v0.43.22-helm
, and tried adding the following environment variables for worker
deployments:
β’ SENTRY_DSN: <dsn>
, as documented in:
β¦ https://docs.airbyte.com/operator-guides/configuring-airbyte#worker
β¦ https://docs.airbyte.com/operator-guides/sentry-integration/
β’ JOB_ERROR_REPORTING_STRATEGY: sentry
and JOB_ERROR_REPORTING_SENTRY_DSN: <dsn>
as hinted in:
β¦ https://github.com/airbytehq/airbyte/issues/7957#issuecomment-1297672827
β¦ https://github.com/airbytehq/airbyte/issues/18755
β¦ https://airbytehq.slack.com/archives/C021JANJ6TY/p1681193093461609
β¦ https://github.com/airbytehq/airbyte-platform/blob/main/airbyte-config/config-models/src/main/java/io/airbyte/config/EnvConfigs.java
β¦ https://github.com/airbytehq/airbyte-platform/blob/main/airbyte-config/config-models/src/main/java/io/airbyte/config/Configs.java
β’ adding SENTRY_ENVIRONMENT: <env>
to the mix
β¦ though, this variable is not referenced anywhere in the Airbyte / Airbyte Platform codebase
Here is the relevant excerpt from our `values.yaml`:
worker:
extraEnv:
- name: JOB_ERROR_REPORTING_STRATEGY
value: "SENTRY"
- name: JOB_ERROR_REPORTING_SENTRY_DSN
valueFrom:
secretKeyRef:
name: airbyte-sentry-dsn
key: dsn
The values are properly set for worker
deployments and pods, but are not set by the worker
when scheduling and instantiating jobs
pods with source and destination connector containers.
Has anyone been able to setup Sentry with Airbyte running on Kubernetes?Jake Kagan
05/31/2023, 5:40 PMOctavia Squidington III
05/31/2023, 7:45 PMSimon Thelin
06/01/2023, 7:28 AMSimon Thelin
06/01/2023, 7:55 AMMAX_NOTIFY_WORKERS
MAX_SYNC_WORKERS
MAX_SPEC_WORKERS
MAX_CHECK_WORKERS
MAX_DISCOVER_WORKERS
Simon Thelin
06/01/2023, 9:50 AM2023-06-01 08:44:08.841 UTC [22] PANIC: could not locate a valid checkpoint record
With the airbyte postgres?Octavia Squidington III
06/01/2023, 1:45 PMPedro Doria
06/01/2023, 1:54 PMSimon Thelin
06/01/2023, 5:17 PMHuib
06/01/2023, 7:34 PMNico Gallinal
06/02/2023, 5:46 AMOmar Allouache
06/02/2023, 11:17 AM"level":"fatal","ts":"2023-06-02T10:01:51.660Z","msg":"ListenIP failed, unable to parse bindOnIP value","address":"192.168.128.4 192.168.144.2"
I have added this .env var
to the airbyte-temporal docker-compose
:
- BIND_ON_IP=0.0.0.0
- TEMPORAL_BROADCAST_ADDRESS=127.0.0.1
kapa.ai
06/02/2023, 3:42 PMdocker-compose up
to spin up all Airbyte containers. 8. After the Airbyte banner shows up in the log, navigate to localhost:8000 to access the Airbyte UI. For more detailed instructions, please refer to the Airbyte Video Tutorial on YouTube: [How To Setup Your Development Environment In Windows Using WSL For Airbyte]() Additionally, you can follow the [Local Deployment](https://docs.airbyte.com/deploying-airbyte/local-deployment) guide in the Airbyte documentation for more information on setting up Airbyte locally.Nick Mancini
06/02/2023, 3:49 PM.env: line 70: SYNC_JOB_INIT_RETRY_TIMEOUT_MINUTES:: command not found
I can't seem to find this specific message anywhere. The closest thing I found mentioned a difference between windows line endings instead of unix line endings, so I tried running dos2unix on the script but the issue persists.1 Can anyone point me in the right direction?
Here's the verbose script output:
XXXX@XXXXXXX:~/airbyte$ sudo ./run-ab-platform.sh -x
./run-ab-platform.sh:14: shift
./run-ab-platform.sh:14: tput cols
./run-ab-platform.sh:14: test 175 -ge 64
./run-ab-platform.sh:14: echo -e '\033[32m'
./run-ab-platform.sh:14: echo -e ' ββββββ ββββββββββ βββββββ βββ ββββββββββββββββββββ'
ββββββ ββββββββββ βββββββ βββ ββββββββββββββββββββ
./run-ab-platform.sh:14: echo -e 'βββββββββββββββββββββββββββββββ βββββββββββββββββββββ'
βββββββββββββββββββββββββββββββ βββββββββββββββββββββ
./run-ab-platform.sh:14: echo -e 'βββββββββββββββββββββββββββ βββββββ βββ ββββββ '
βββββββββββββββββββββββββββ βββββββ βββ ββββββ
./run-ab-platform.sh:14: echo -e 'βββββββββββββββββββββββββββ βββββ βββ ββββββ '
βββββββββββββββββββββββββββ βββββ βββ ββββββ
./run-ab-platform.sh:14: echo -e 'βββ βββββββββ βββββββββββ βββ βββ ββββββββ'
βββ βββββββββ βββββββββββ βββ βββ ββββββββ
./run-ab-platform.sh:14: echo -e 'βββ βββββββββ ββββββββββ βββ βββ ββββββββ'
βββ βββββββββ ββββββββββ βββ βββ ββββββββ
./run-ab-platform.sh:14: echo -e ' Move Data'
Move Data
./run-ab-platform.sh:14: echo -e '\033[0m'
./run-ab-platform.sh:14: sleep 1
./run-ab-platform.sh:14: docker compose version
./run-ab-platform.sh:14: Download
./run-ab-platform.sh:14: for file in $all_files
./run-ab-platform.sh:14: test -f docker-compose.yaml
./run-ab-platform.sh:14: find docker-compose.yaml -type f -mtime +60
./run-ab-platform.sh:14: test
./run-ab-platform.sh:14: echo -e '\033[94mfound docker-compose.yaml locally!\033[39m'
found docker-compose.yaml locally!
./run-ab-platform.sh:14: for file in $all_files
./run-ab-platform.sh:14: test -f docker-compose.debug.yaml
./run-ab-platform.sh:14: find docker-compose.debug.yaml -type f -mtime +60
./run-ab-platform.sh:14: test
./run-ab-platform.sh:14: echo -e '\033[94mfound docker-compose.debug.yaml locally!\033[39m'
found docker-compose.debug.yaml locally!
./run-ab-platform.sh:14: for file in $all_files
./run-ab-platform.sh:14: test -f .env
./run-ab-platform.sh:14: find .env -type f -mtime +60
./run-ab-platform.sh:14: test
./run-ab-platform.sh:14: echo -e '\033[94mfound .env locally!\033[39m'
found .env locally!
./run-ab-platform.sh:14: for file in $all_files
./run-ab-platform.sh:14: test -f .env.dev
./run-ab-platform.sh:14: find .env.dev -type f -mtime +60
./run-ab-platform.sh:14: test
./run-ab-platform.sh:14: echo -e '\033[94mfound .env.dev locally!\033[39m'
found .env.dev locally!
./run-ab-platform.sh:14: for file in $all_files
./run-ab-platform.sh:14: test -f flags.yml
./run-ab-platform.sh:14: find flags.yml -type f -mtime +60
./run-ab-platform.sh:14: test
./run-ab-platform.sh:14: echo -e '\033[94mfound flags.yml locally!\033[39m'
found flags.yml locally!
./run-ab-platform.sh:14: for file in $dot_env $dot_env_dev
./run-ab-platform.sh:14: echo -e '\033[94mLoading Shell Variables from .env...\033[39m'
Loading Shell Variables from .env...
./run-ab-platform.sh:14: source .env
./run-ab-platform.sh:14: VERSION=0.44.8
./run-ab-platform.sh:14: CONFIG_ROOT=/data
./run-ab-platform.sh:14: DATA_DOCKER_MOUNT=airbyte_data
./run-ab-platform.sh:14: DB_DOCKER_MOUNT=airbyte_db
./run-ab-platform.sh:14: WORKSPACE_ROOT=/tmp/workspace
./run-ab-platform.sh:14: WORKSPACE_DOCKER_MOUNT=airbyte_workspace
./run-ab-platform.sh:14: LOCAL_ROOT=/tmp/airbyte_local
./run-ab-platform.sh:14: LOCAL_DOCKER_MOUNT=/tmp/airbyte_local
./run-ab-platform.sh:14: HACK_LOCAL_ROOT_PARENT=/tmp
./run-ab-platform.sh:14: BASIC_AUTH_USERNAME=airbyte
./run-ab-platform.sh:14: BASIC_AUTH_PASSWORD=password
./run-ab-platform.sh:14: BASIC_AUTH_PROXY_TIMEOUT=900
./run-ab-platform.sh:14: DATABASE_USER=docker
./run-ab-platform.sh:14: DATABASE_PASSWORD=docker
./run-ab-platform.sh:14: DATABASE_HOST=db
./run-ab-platform.sh:14: DATABASE_PORT=5432
./run-ab-platform.sh:14: DATABASE_DB=airbyte
./run-ab-platform.sh:14: DATABASE_URL=jdbc:<postgresql://db:5432/airbyte>
./run-ab-platform.sh:14: JOBS_DATABASE_MINIMUM_FLYWAY_MIGRATION_VERSION=0.40.26.001
./run-ab-platform.sh:14: CONFIG_DATABASE_USER=
./run-ab-platform.sh:14: CONFIG_DATABASE_PASSWORD=
./run-ab-platform.sh:14: CONFIG_DATABASE_URL=
./run-ab-platform.sh:14: CONFIGS_DATABASE_MINIMUM_FLYWAY_MIGRATION_VERSION=0.40.23.002
./run-ab-platform.sh:14: TEMPORAL_HOST=airbyte-temporal:7233
./run-ab-platform.sh:14: INTERNAL_API_HOST=airbyte-server:8001
./run-ab-platform.sh:14: CONNECTOR_BUILDER_API_HOST=airbyte-connector-builder-server:80
./run-ab-platform.sh:14: WEBAPP_URL=<http://localhost:8000/>
./run-ab-platform.sh:14: CONNECTOR_BUILDER_API_URL=/connector-builder-api
./run-ab-platform.sh:14: SYNC_JOB_MAX_ATTEMPTS=3
./run-ab-platform.sh:14: SYNC_JOB_MAX_TIMEOUT_DAYS=3
./run-ab-platform.sh:14: SYNC_JOB_INIT_RETRY_TIMEOUT_MINUTES: 5
.env: line 70: SYNC_JOB_INIT_RETRY_TIMEOUT_MINUTES:: command not found
Caio CΓ©sar P. Ricciuti
06/02/2023, 5:34 PMself-hosted
instances, I was looking into the docs and only mention Airbyte cloud... Have anyone used the API hosting airbyte yourself? TIAOctavia Squidington III
06/02/2023, 7:45 PMSharat Visweswara
06/02/2023, 7:55 PMKing Ho
06/05/2023, 6:53 AM