Unable to access Airbyte UI via airbyte-webapp-svc, only by direct IP to pod

Troubleshooting
, ,
#1
  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Windows Server 2019 accessing Kubernetes on Azure
  • Memory / Disk: not sure
  • Deployment: Kubernetes
  • Airbyte Version: 0.35.65-alpha
  • Description: Using CRDs from kube/overlays/stable for installation. Trying to connect to the airbyte-webapp-svc and/or its associated IP address does not resolve to the Airbyte UI. If I access the IP of the backend pod directly I can bring up the Airbyte UI and it functions normally. If I try to access the UI via the IP address of the airbyte-webapp-svc service it times out. Running curl against the IP of the airbyte-webapp-svc also times out.

Here is the configuration of the webapp service:

apiVersion: v1
kind: Service
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"airbyte-webapp-svc","namespace":"airbyte"},"spec":{"ports":[{"port":80,"protocol":"TCP"}],"selector":{"airbyte":"webapp"},"type":"ClusterIP"}}
  creationTimestamp: "2022-04-18T22:00:25Z"
  name: airbyte-webapp-svc
  namespace: airbyte
  resourceVersion: "22509560"
  uid: 89c48b2a-0abe-44ea-ba4b-ce686961ee52
spec:
  clusterIP: 10.0.x.x (masked for privacy)
  clusterIPs:
  - 10.0.x.x (masked for privacy, same IP as above)
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - port: 80
    protocol: TCP
    targetPort: 80
  selector:
    airbyte: webapp
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}
#2

What command are you doing to port-forward the access to the Airbyte service?

#4

Instead of using a command I have a gateway and virtual service set up for data to go to the airbyte-webapp-svc service. The main reason for this is because in order to use the port forwarding command (kubectl port-forward svc/airbyte-webapp-svc 8000:80 --namespace airbyte) it requires a separate command window to be running at all times on the Windows Server used to access Kubernetes.

#5

but if you use port-forward it works?

#6

It only works if I use localhost:8000 or the IP of the current web app pod from my Windows machine in Chrome/Firefox. If I try to use the IP of the airbyte-webapp-svc it does not resolve and times out.

#7

For that I think you need to create a nginx service and allow to connect to the service. See docs in Kubernetes: Connecting Applications with Services | Kubernetes

#8

Thank you for the info. Can you confirm that the nginx service and/or load balancer needs to be pointed at the service called airbyte-webapp-svc? This seems to be where things get lost. I’ve pointed it to “airbyte-webapp-svc” and “webapp” and neither will resolve. I’m using the stock install of Airbyte from Github.

#9

Yes, I made one example using Google GKE. I’d changed the type of airbyte-webapp-servicefrom NodePort to LoadBalancer after redeploying it should works.