Summary
The user noticed a change in the way the AIRBYTE_API_HOST environment variable in ConfigMap is created with the latest Helm chart version 0.383.1 compared to the previous version 0.263.0. The user is questioning whether this change is a bug or if they should set the environment variable elsewhere to override the one in ConfigMap.
Question
I’ve noticed that with the latest helm chart (0.383.1) the way the AIRBYTE_API_HOST env var in ConfigMap gets created changed.
template now - https://artifacthub.io/packages/helm/airbyte/airbyte/0.383.1?modal=template&template=env-configmap.yaml|https://artifacthub.io/packages/helm/airbyte/airbyte/0.383.1?modal=template&template=env-configmap.yaml
before (version we use) - https://artifacthub.io/packages/helm/airbyte/airbyte/0.263.0?modal=template&template=env-configmap.yaml|https://artifacthub.io/packages/helm/airbyte/airbyte/0.263.0?modal=template&template=env-configmap.yaml
So before the upgrade, our value was (global.edition wasn’t set, so defaulted to community )
AIRBYTE_API_HOST: http://{{ .Release.Name }}-airbyte-server-svc:{{ .Values.server.service.port}}/api/public
But with the latest charts, without setting the global.edition (which still defaults to community ) :
AIRBYTE_API_HOST: http://localhost:{{ .Values.server.service.port }}/api/public
Given that there are only 3 global.edition values: pro, community and enterprise, the last value (the one we had before) can be achieved only by specifying an invalid edition like edition: "" , which seems to break other functionalities in the chart.
Just wanted to see if this is a bug, or I should set the env var elsewhere to override the one in ConfigMap.
Thanks!
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.