I'm running into an interesting issue (well, 2 actually). I'm deploying Airbyte as a subchart of a parent helm chart. This was the preferred approach since I have several interdependent components (e.g.

pgbouncer

). The first issue is that the

bootloader

chart is preventing anything else to deploy since it is a

pre-install

,

pre-upgrade

hook. The problem is that the

bootloader

is dependent on

pgbouncer

for the metadata db connection. I can get around this locally by installing with the

bootloader

disabled, then upgrading with the

bootloader

enabled. I could also split airbyte into its own chart and install everything else first, then install airbyte. I'd much rather keep everything together from a maintenance standpoint. The second issue is a bit weird and more of a strange bug in

helm

, but I believe it should be considered in regards to the Airbyte chart. For some reason, the

ternary

function in the

_helpers.tpl

template doesn't honor the parent chart's

values.yaml

if there is an override of the parent chart's value file. This matters because of environment configurations. For instance, I have Airbyte as a subchart within my main helm chart. This parent chart has a

values.yaml

for general and default values. I then have a local environment

values.yaml

that overrides some of the parent chart's defaults. What happens is that if I don't explicitly set the database connection values in the local env

values.yaml

, the templates get rendered with the default airbyte values. It might be a good idea to consider using a different function than the

ternary

function to set these values.

Based on the information provided in the extracts, it seems you're facing two issues related to deploying Airbyte using Helm charts. 1. The

bootloader

chart is preventing other components from deploying due to its

pre-install

,

pre-upgrade

hook. This is a tricky situation as the

bootloader

is dependent on

pgbouncer

for the metadata db connection. Unfortunately, the extracts do not provide a direct solution to this issue. However, as you mentioned, one workaround could be to install with the

bootloader

disabled, then upgrade with the

bootloader

enabled. Alternatively, you could consider splitting Airbyte into its own chart and install everything else first, then install Airbyte. 2. The second issue is related to the

ternary

function in the

_helpers.tpl

template not honoring the parent chart's

values.yaml

if there is an override of the parent chart's value file. This seems to be a Helm-specific issue and might be better addressed in Helm-specific forums or communities. However, as a workaround, you could consider explicitly setting the database connection values in the local env

values.yaml

to ensure the templates get rendered with the correct values. Unfortunately, the extracts do not provide a direct solution or alternative function to the

ternary

function issue. It might be beneficial to raise this issue in the Airbyte community or Helm community for more specific guidance. For more information on deploying Airbyte on Kubernetes using Helm, you can refer to the [official documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm).