Closed Kamaradeivanov closed 12 months ago
Same behaviour with chart in version 0.45.31 and app in version 0.43.1. I try an old one just in case.
Problem solved !
One of my mutating webhooks took almost 10 seconds to answer, so each create call to the api-server took more than 10sec to answer, but airbyte-worker has a timeout of 10sec.
To find the problem I've checked the log of the api-server on the GKE console. Latency appear in labels :
apiserver.latency.k8s.io/serialize-response-object: "6.336689ms"
apiserver.latency.k8s.io/mutating-webhook: "9.995078933s"
apiserver.latency.k8s.io/total: "10.007804155s"
apiserver.latency.k8s.io/response-write: "824ns"
@Kamaradeivanov I have exactly the same issue. Can you provide some detail on how you resolved it?
Hi @edfincham you should check your api-server to see if there is no timeout request. If you are on a managed kubernetes ask your cloud provider, personally I was on GKE and logs are available through the console.
You can also edit all your validatingwebhookconfigurations
and mutatingwebhookconfigurations
to reduce the timeoutSeconds
below 10 (because airbyte have harcoded the timeout to 10s)
kubectl edit mutatingwebhookconfigurations
kubectl edit validatingwebhookconfigurations
mutatingwebhookconfigurations
Worked a treat - thank you :slightly_smiling_face:
What method are you using to run Airbyte?
Kubernetes
Platform Version or Helm Chart Version
Chart 0.49.22 - App 0.50.34
What step the error happened?
During the Sync
Revelant information
I recently setup airbyte with the last helm chart (0.49.22) on a GKE v1.27.4 cluster. I just overide configuration regarding ingress for webapp.
Install is fine, web app is accessible with the URI configure in the ingress host.
Error appear when I try to create a source, I try with certified Postgres and MongoDb connectors. After the click on
Set up source
button, errors appear on 2 pods :There is no pod or job e-mongodb-v2-check-xxxxxxxxxxxxxx that appear in my kubernetes namespace.
I check RBAC access but everithing seems fine : ServiceAccount
airbyte-admin
, Roleairbyte-admin-role
and RoleBindingsairbyte-admin-binding
exists.Role is setting following rules :
All pods are using the
airbyte-admin
service account.Relevant log output