Open firehist opened 3 weeks ago
Waouh, problem fixed by removing the http://
prefix in the INTERNAL_API_HOST
environment variable (coming from airbyte-airbyte-env
config map).
It can be related to the latest chart release ? https://artifacthub.io/packages/helm/airbyte/airbyte/0.101.2?modal=template&template=airbyte-db.yaml&compare-to=0.94.1
Thanks for reporting the issue @firehist I added this to deployment team backlog for further investigation
Helm Chart Version
0.101.2
What step the error happened?
Other
Relevant information
We are running Airbyte, thanks to the official helm chart in version 0.101.2.
We are using external Google Secret Key Manager, Google Cloud Storage and our PostgreSQL on Google Cloud SQL as external in our values.yaml.
Everything is working well, except when I have the great idea to scale up worker > 1.
Other workers will fail with the attached log ouput.
It seems to receive a string
//airbyte-airbyte-server-svc"
which should be the internal API HOST or something like that, but theparsePort()
fails, as there is no port in this string... The second worker POD definition is exactly the same than for the first one, as it is controlled by a Deployment.Relevant log output