but webapp requires it CONNECTOR_BUILDER_API_HOST

Hello Krzysztof. Please use threads instead of multiple messages in the channel. If you have questions about it read Airbyte's Slack code of conduct: https://docs.airbyte.com/project-overview/slack-code-of-conduct

I'm facing this same issue with airbyte v.0.40.21.

@Krzysztof @Leonardo de Almeida can you describe better what are you trying to do? Are you deploying Airbyte with Helm or using Docker?

@Marcos Marx (Airbyte) I am seeing the same error as @Krzysztof. I am using helm charts to deploy 0.41.0 onto AWS EKS. I am using 100% defaults except for 1) namespace and 2) nodeSelector. I want airbyte running in a particular tenant on AWS. If I deploy 0.40.46 using the same configuration I do not see the error.

I see, the variable was added in PR 19269. The team is investigating the solution for this issue, but until now the workaround is to use previous version of the Airbyte Platform.

I'm deploying airbyte in kubernetes using kustomize and manifests present in branch master. When I updated manifests and .env I've added some new envs but the

CONNECTION_BUILDER_API_HOST

was not in

.env

file. Even searching in github for the variable, I could not find any default value, so I have to downgrade version to

v0.40.14

. I've facing another issue too... Sometimes I've notice that sync workers could not start, even when check was succeeded (I'm talking about postgres source and s3 destinations), and when I'm trigger

retest source

and

discovery schema

from airbyte UI, the pod which make the connection and fetch schemas didn't show in my k8s namespace and seems that is a intermittent behavior cause sometimes the pods are triggered normally.

Team is currently investigating the issue. ASAP there any solution I’ll return here.

Thank you for you return @Marcos Marx (Airbyte), and about the second issue with discovery schema? You guys already have notice that possible bug? I suspect that even the syncs are failing because of this intermittence in triggering new pods. There are some logs in my syncs. The sync continues to have these errors until a moment when the sync works, and this happens in all syncs and I realized that it started after updating to v0.40.14.

This thread is about the problem with env variable. Please post a new message about any other issue.