@kapa.ai Is there a way for me to indicate via helm values, the image of the mongodb destination connector ?

The knowledge sources do not explicitly mention a way to pin or specify a specific connector image version (such as the MongoDB destination connector) directly via Helm

values.yaml

on a per-connector basis. What the documentation does describe is a global custom image registry configuration, which redirects all platform and connector image pulls to a registry you control. Here's how that works: 1. Set a custom registry in your `values.yaml`:

global:
  image:
    registry: ghcr.io/NAMESPACE

2. Push the specific connector image (e.g., a pinned version of the MongoDB destination) to your custom registry:

docker pull airbyte/destination-mongodb:<your-desired-version>
docker tag airbyte/destination-mongodb:<your-desired-version> ghcr.io/NAMESPACE/destination-mongodb:<your-desired-version>
docker push ghcr.io/NAMESPACE/destination-mongodb:<your-desired-version>

This way, Airbyte will pull connector images from your registry, where you control which version is available. [Custom Image Registry] However, there is a known open GitHub issue requesting the ability to pin connector versions directly in

values.yaml

, which suggests this is not currently supported as a native per-connector Helm value. [GitHub Issue] In summary, you cannot directly specify the MongoDB destination connector image in Helm values on a per-connector basis today. The workaround is to use a custom image registry and control which image versions are available there. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.