How can I override the default version of a connector when deploying Airbyte on Kubernetes?

New message text here

I want to set default connector versions so they are not overridden during Airbyte’s startup. Is it possible? How can I achieve this?

@Adrien Chaussende can you talk more about your use case? connectors you are already using should not have their default versions changed during start up. what exactly is the behavior you're seeing and what are you going for?

@Ella Rohm-Ensing (Airbyte) Sure! Here is some context around my question: Airbyte is in v0.44.5 and is deployed on Kubernetes using the official Helm chart and ArgoCD. We use the Salesforce Source connector in v2.0.2. We rolled out a change on Airbyte by changing the ingress of it. It made the instance to be restarted (I think the bootloader ran at this point). After that, the Salesforce connector version was v2.0.12. It created an issue in our data because it didn’t collect all the data we expected. Downgrading to v2.0.2 was the workaround for this. As another example, I also noticed that the TikTok Marketing connector was downgraded to v3.1.0 after the restart. We expected to be in v3.4.0. My goal is then to avoid these unexpected changes in connector versions by overriding the default version for a connector.

I found the same issue is occurring in Helm chart v0.49.5. Is there a workaround?

Hi @堤利史, I cross-posted on #C021JANJ6TY here You can override the connectors catalog to do so. I didn’t try it yet 🙂

Oh, I missed the post. Thanks!