Hey there! I'm doing some research on deploying a small airbyte setup (just a few GB database sources). Our normal setup is k8s, but given that the aibyte's k8s-deployment is still in beta, there are some known_issues, and how easy it is to

docker-compose up

on a VM, I'm leaning towards just using

docker-compose

. The biggest advantage of the k8s deployment is the scalability, which in our setup is most likely not needed. So I'm wondering how stable the k8s beta deployment is? When is the beta

deployment

moving to

stable

?

We are evaluating Airbyte, and all our stack is mainly in k8s already (Airflow, Seldon and etc), so our preference would be to push to k8s, using a published helm chart. Just as @Stefan Otte here, I would like to know more about the whole roadmap to make the deployments to k8s a bit more smoothly. Thanks!

Hi @Stefan Otte, if you have already applications running on K8S I'll suggest you to give a try to our K8S deployment. In case you'll face any issue we'll be happy to help you. You can give a try to the helm chart on our repo or kustomize. Airbyte configurations can be exported so in case you want to fallback to a

docker-compose

you won't need to go through manual config again. Moreover you'll find plenty of user on this slack to give you feedback around K8S, and if you have any specific question we're here for help.

Thanks for your responses. We'll evaluate our options. I still lean towards

docker-compose

and as "Airbyte configurations can be exported" the upgrade path to k8s is also there.