Airbyte OSS on GKE returning 504 error

Summary

Airbyte OSS running on GKE is returning 504 error when accessing the webapp. Traefik logs show 200 for initial requests and 499 for subsequent ones. CPU and memory requests are within limits. Setup is behind VPN.


Question

Hello Channel ,
I have airbyte oss(appVersion: 0.50.56) on gke running from last one year ,this is the only application running on the whole cluster
Suddenly i am getting 504 and not able to open the webapp
all the cpu and memory request are within limit , workder nodes are 4cpu and 16gb ram
My Traefik logs get 200 for initial few request for the assets and the later are retuning 499 for all the other requests
My ingressroute is pointed to the webapp on port 80
kubectl port-forwarding it to local i am able to access my app perfectly and my jobs are still running
This setup is behind VPN
Any leads on debugging this issue will be helpful
Also tried adding below to traefik
spec:
forwardingTimeouts:
dialTimeout: 120s
responseHeaderTimeout: 300s
idleConnTimeout: 300s



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-oss", "gke", "504-error", "traefik", "vpn", "debugging"]