Hey that works for us - thanks! I was able to get the latest version of the Airbyte Helm chart v 1.2.0 deployed using S3:
-
EKS cluster without Karpenter:
https://console.qovery.com/organization/5fafa1c2-689c-4a54-8ea1-533a7230a2a5/project/8fdd5013-c37f-45af-928a-a3b88179e1ef/environment/72031385-01d8-444d-b25d-63177c6f2dc7/services/general -
EKS cluster with Karpenter
https://console.qovery.com/organization/5fafa1c2-689c-4a54-8ea1-533a7230a2a5/project/8fdd5013-c37f-45af-928a-a3b88179e1ef/environment/e80b4911-d8a5-4d56-9477-6525e5ea49ec/services/general
You have to be careful with the node sizes if Karpenter is enabled I think, see: Scaling Airbyte | Airbyte Documentation
EDIT: I removed the above environments since both are working; will replace with a more permanent one later.
Don’t worry about the minio airbyte pod; we’re not going to use it in production. I’ll also try using an external AWS managed database service with Airbyte: