Open hongbo-miao opened 2 weeks ago
I found a clean solution. I posted at https://stackoverflow.com/a/78644975/2000548 😃
Here is a copy:
After I change from
global
database:
# ...
secretName: production-hm-airbyte-secret
user: airbyte_user
passwordSecretKey: POSTGRES_PASSWORD
# ...
to
global
database:
# ...
secretName: production-hm-airbyte-secret
userSecretKey: POSTGRES_USER_NAME
passwordSecretKey: POSTGRES_PASSWORD
# ...
It does not expect DATABASE_USER
any more and can deploy smoothly!
I think users would expect user: airbyte_user
should also work though. I will leave it open. Thanks!
Thanks for reporting the issue @hongbo-miao I added this to the deployment team take a look
Helm Chart Version
0.199.0
What step the error happened?
On deploy
Relevant information
Originally asked at Stack Overflow, here is a copy:
I am trying to deploy Airbyte to Amazon EKS by its helm chart. I am using Airbyte v0.63.1 and Helm chart v0.199.0.
Based on this tutorial, I have created Kubernetes secret
production-hm-airbyte-secret
in advance with valuesAWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
LOG_S3_BUCKET_NAME
LOG_S3_BUCKET_REGION
POSTGRES_USER_NAME
POSTGRES_PASSWORD
Based on this original values.yaml, here is my-values.yaml:
However, after I deploy Airbyte Helm chart v0.199.0, I got error inside pod "airbyte-airbyte-bootloader":
Also, I noticed Airbyte created a secret
airbyte-airbyte-secrets
during deployment with valuesDEFAULT_MINIO_ACCESS_KEY
DEFAULT_MINIO_SECRET_KEY
WORKLOAD_API_BEARER_TOKEN
And missing
DATABASE_USER
inside.I try to append
airbyte-bootloader
section in my-values.yaml. Bothand
will give error
I searched online and found
But none of them provides a solution.
Any guide would be appreciate, thanks!
My Current Workaround Solution
I found a workaround solution which is patching Kubernetes secret
airbyte-airbyte-secrets
to add missingDATABASE_USER
immediately after deployment.Then airbyte-airbyte-bootloader can pick up this
DATABASE_USER
from Kubernetes secretairbyte-airbyte-secrets
value.