Hello Experts,
I am deploying airbyte using helm chart(s) on k8s
All the POD(s) are up and running fine. No error reported in console logs.
$ kubectl get pod
NAME READY STATUS RESTARTS AGE
airbyte-db-0 1/1 Running 1 (2d4h ago) 2d4h
airbyte-minio-0 1/1 Running 0 2d4h
airbyte-poc-airbyte-bootloader 0/1 Completed 0 2d4h
airbyte-poc-connector-builder-server-76f4cd4d56-pvvjz 1/1 Running 0 2d4h
airbyte-poc-cron-7f5887bbb4-jfn7r 1/1 Running 0 2d4h
airbyte-poc-pod-sweeper-pod-sweeper-5f7df54649-wxmht 1/1 Running 0 2d4h
airbyte-poc-server-5f654cc96f-zzxvs 1/1 Running 0 2d4h
airbyte-poc-temporal-cc4bdfc9c-2x7jr 1/1 Running 0 2d4h
airbyte-poc-webapp-77bb956f-dzpjt 1/1 Running 0 22h
airbyte-poc-worker-f698cf94d-448z5 1/1 Running 0 2d4h
While accessing the UI getting “Cannot reach server. The server may still be starting up.” which looks like common error but couldn’t find what could be the reason I am able to reach airbyte server from the airbyte webapp.
/ # env | grep -i 8001
INTERNAL_API_HOST=airbyte-poc-airbyte-server-svc:8001
AIRBYTE_POC_AIRBYTE_SERVER_SVC_PORT_8001_TCP=tcp://192.168.248.110:8001
AIRBYTE_POC_AIRBYTE_SERVER_SVC_SERVICE_PORT=8001
AIRBYTE_POC_AIRBYTE_SERVER_SVC_PORT=tcp://192.168.248.110:8001
AIRBYTE_POC_AIRBYTE_SERVER_SVC_SERVICE_PORT_HTTP=8001
AIRBYTE_POC_AIRBYTE_SERVER_SVC_PORT_8001_TCP_ADDR=192.168.248.110
AIRBYTE_POC_AIRBYTE_SERVER_SVC_PORT_8001_TCP_PORT=8001
AIRBYTE_POC_AIRBYTE_SERVER_SVC_PORT_8001_TCP_PROTO=tcp
$ kubectl exec -it airbyte-poc-webapp-77bb956f-dzpjt sh
/ # curl 192.168.248.110:8001/health
{"status":"UP"}/
Can anyone pls provide some input for further troubleshooting?