Error adding custom source connector to Airbyte UI in Kubernetes Cluster

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

The user is facing an issue when trying to add a custom source connector to Airbyte UI in a Kubernetes Cluster. The error message ‘Airbyte is temporarily unavailable. Please try again. (HTTP 502)’ is displayed after a few minutes of loading. The user has deployed Airbyte via Helm in a private Kubernetes Cluster with kubenet networking. The source connector pod starts in the cluster but fails after a few seconds.


Question

Hi guys, I have a problem creating a custom source connector. I build it and tested it successfully. Then I created a Docker Image and pushed the image into my Azure Container Registry. When I try to add the connector from the Airbyte UI, after a few minutes loading I get the error Airbyte is temporarily unavailable. Please try again. (HTTP 502). Airbyte (version 1.0.0, but I tried earlier versions as well) is deployed via Helm in a private Kubernetes Cluster with kubenet networking. After clicking the add button, the pod starts in the cluster, but fails after a few seconds. I attached a screenshot of the source connector pod logs.
Does someone have an idea?


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.

Join the conversation on Slack

["custom-source-connector", "airbyte-ui", "kubernetes-cluster", "http-502", "helm", "kubenet-networking"]
2

First line:
main Entrypoint was not set! AIRBYTE_ENTRYPOINT must be set in the container.

3

Did you build with airbyte-ci ... or docker build ... ?

4

<@U05JENRCF7C> docker build. This is the content of my dockerfile: https://discuss.airbyte.io/t/building-docker-image-for-forked-source-connector-with-patch/5127/2

5

I’d recommend uncommenting

ENTRYPOINT ["python", "/airbyte/integration_code/main.py"]```
and rebuilding Docker image
6

<@U05JENRCF7C> Thanks, now it works.