Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support deployment on Kubernetes #835

Closed
michel-tricot opened this issue Nov 6, 2020 · 1 comment · Fixed by #1135
Closed

Support deployment on Kubernetes #835

michel-tricot opened this issue Nov 6, 2020 · 1 comment · Fixed by #1135
Assignees
Labels
type/enhancement New feature or request
Milestone

Comments

@michel-tricot
Copy link
Contributor

michel-tricot commented Nov 6, 2020

Tell us about the problem you're trying to solve

I would like to deploy Airbyte on K8s

Impl

  • Support the following platforms: minikub, GKE, EKS)
  • documentation for each

Additional Context

  • whoever works on this, please split this into separate issues for each platform if it makes sense to do so.
@michel-tricot michel-tricot added the type/enhancement New feature or request label Nov 6, 2020
@michel-tricot
Copy link
Contributor Author

some infos from @guillaumelachaud (#1102):

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants