Stability of Helm chart versions for Airbyte on EKS cluster

Summary

Inquiring about the stability of different Helm chart versions for deploying Airbyte on an EKS cluster and whether frequent updates indicate improvements or bug fixes.


Question

Hi everyone, we are looking into deploying Airbyte on an EKS cluster using the Helm.
I have noticed that Helm chart are updated very frequently and was wondering whether this is a reflection of improvements of bugfixing and instalbility.
Is there a Helm chart version that those of you who installed it would say is a stable one?
Thanks.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["airbyte", "eks-cluster", "helm-chart", "stability", "updates", "bug-fixes"]

<@U035912NS77> had more experience with our helm over EKS I think, but in general it’s both. General use cases should be stable though.

<@U062NLT304F> Yep, in general I’ve found the most recent versions of the charts to be most reliable as there have been a lot of little fixes there. a few builds back there was some weirdness with some of the recent config changes (the Airbyte team has been working to heavily consolidate config, creating more unified options for setting up things like external storage if you’re using S3—there was a bit of a transition in the midst of that though).

There’s still a few awkward bits (like some redundant config when you’re using external databases), but it’s come a long way.

Especially with the changes to config and features features like AWS Secrets Manager (if you’re using it), I’d say the latest will be your smoothest option. and are much easier for those of us who hang out around here to assist with compared to builds against older chart versions.