- 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: {}