Open aqeelat opened 6 months ago
Documentation was updated describing how to setup using S3. There is a work being done to update and show how to do using GCS. https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#external-airbyte-database
I'll keep the issue open for the team take a look related to the other issues reported.
@marcosmarxm regarding that, I think the point number 5 should be unchecked because it does not make sense to have to define the secret and key in multiple places. Also, the point of using helm is to not have to update k8s manifests by hand. The issue is trivial and we can just update the bootloader or any place that uses DATABASE_PASSWORD to use the externalDatabase.secretName if it exists.
I can open a PR if that would convince you
@aqeelat thanks but at the moment Deployment team is already working to refactor and improve this part.
Helm Chart Version
0.53.159
What step the error happened?
On deploy
Revelant information
There are a few issues/inconsistencies in how the helm charts are generated.
Error: UPGRADE FAILED: template: airbyte/templates/env-configmap.yaml:15:21: executing "airbyte/templates/env-configmap.yaml" at <.Values.webapp.api.url>: nil pointer evaluating interface {}.url
state-storage
but the minio tamplate has a script for creating two bucketsstate-storage
andairbyte-dev-logs
global.database.secretName
andglobal.database.secretValue
even though we're using.Values.externalDatabase.existingSecret
because of the bootloader https://github.com/airbytehq/airbyte-platform/blob/v0.50.50/charts/airbyte-bootloader/templates/pod.yaml#L63helm --version 0.53.159
uses image version 0.50.49 even though I ranhelm repo update
# -- Log4j configuration file, if not using minio, update to "log4j2-no-minio.xml"
does not indicate which file to use with external minioI will add any other issues I encounter.
I can open a PR to fix some of these issues.
Relevant log output
No response