You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I definitely can share them but ultimately, I didn't manage to completely deploy Airbyte over K8s. Here's a quick recap of what's not working yet (though it's not the topic of the current ticket):
In order for airbyte-server to be reachable by web-app, it needs to be exposed by a Service and an Ingress. They require a health check to pass before they start routing traffic to it. Which means an endpoint has to return a 200 on a GET request (default is / but it's customizable). Currently only /api/v1/debug is a GET endpoint and can be used for the Ingress healthcheck. But it fails and returns a 500, as the implementation is looking to call the docker executable which the current image doesn't seem to provide
Similarly, the scheduler seems to be involved in some DinD: it mounts the host docker socket and will I guess try to schedule jobs through it. Though it's possible to mount the docker this way in K8s, it's highly discouraged, the K8s cluster could be using another runtime than Docker.
Also, the Helm charts I have written are GCP specific as it uses Cloud IAP to add an authentication mechanism in front of the services.
Tell us about the problem you're trying to solve
I would like to deploy Airbyte on K8s
Impl
Additional Context
The text was updated successfully, but these errors were encountered: