Summary
User is facing a 502 bad gateway error when trying to access Airbyte UI on a private server without FQDN. They have configured the host as airbyte.local and added the private IP to /etc/hosts file. Looking for alternative solutions.
Question
Hi Airbyte team, I am trying to install aibyte using kubernetes on an on prem server that has no FQDN. I followed the instructions in the documentation - https://docs.airbyte.com/deploying-airbyte/
And when it came to configuring ingress, with reference to previous slack conversations, I had put host as airbyte.local as my server don’t have a FQDN. And also added the private ip to my /etc/hosts file in my local machine from where I am trying to use the Airbyte’s Ui.
After that, when I try to access the Ui - I get 502 bad gateway error.
Please let me know if I can try something different to access Airbyte hosted on a private server
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
["airbyte", "kubernetes", "private-server", "ingress", "502-bad-gateway", "FQDN"]
are you sure that your Airbyte deployment works properly?
have you tried port forwarding https://docs.airbyte.com/deploying-airbyte/#6-set-up-port-forward-for-ui-access just to check if it’s fine?
can you install also k9s (https://k9scli.io/) and provide screenshot with pods from namespace where your Airbyte is deployed?
Yes, followed the documentation and faced new issues.
The screenshot:
<@U05JENRCF7C> - also the way I am using airbyte.local in place of host in my ingress configuration - is this the right way? I am new to kubernetes deployment - still picking on the concepts.
Pods look good, so it looks like something is not right on ingress / reverse proxy layer. I’m not sure about airbyte.local.
What do you get for kubectl get ingresses?
Can you provide output kubectl describe ingresses, as describe provide more details?
this part with empty Address got my attention
https://stackoverflow.com/questions/51511547/empty-address-kubernetes-ingress
do you have ingress addon enabled?
minikube addons enable ingress
I have enabled the ingress, and now the address is populated:
If my understanding is correct - I can access airbyte using this ip now?
what do you see when opening airbyte.local in a browser?
I get website not available.
I have also mapped airbyte.local to the external ip of ingress on my local machine
Thanks, I will check this out!