Benjamin 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 -}}
kapa.ai
05/29/2023, 1:39 PMkapa.ai
05/29/2023, 1:40 PMdata-platform-external-secret
contains the key DATABASE_PASSWORD
. However, the error you're encountering is related to the airbyte-bootloader
pod, which is not directly related to the external database configuration. The issue might be caused by a misconfiguration in the Helm chart or an issue with the specific version you're using. Unfortunately, I don't have enough information to give you a confident answer yet. I recommend reviewing the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm) and checking the [Airbyte Slack](https://airbytehq.slack.com) for similar issues or asking for help there.Benjamin Groves
05/29/2023, 2:14 PMDATABASE_PASSWORD
env var to the bootloader:
airbyte-bootloader:
extraEnv:
- name: DATABASE_PASSWORD
valueFrom:
secretKeyRef:
name: data-platform-external-secret
key: DATABASE_PASSWORD
Then redeployed and it worked 🤷♂️