@kapa.ai We are installing using our own container registry so I need to pull/retag/push the images used by Airbyte. We are currently upgrading to helm chart 2.1.1 from 2.0.19. What tag of

airbyte/async-profiler

should I copy to our registry? The image appears to have no semver based tags. It appears to be part of the connector-builder feature. Have there been changes to connector-builder in 2.1.1? Basically, what images (inc tags) should I copy to our registry so that Airbyte can operate? (Not including the connector images, I can find those through the interface after Airbyte is running)

I can partially answer your question, but there are some important gaps in what the knowledge sources cover. Getting the Definitive Image List The most reliable way to get the exact images (with tags) required for a specific Helm chart version is to use `abctl`:

abctl images manifest

This will output the precise list of images and tags for the version you're deploying. [abctl docs] The airbyte/async-profiler Issue You're correct that

airbyte/async-profiler

does not follow standard semver tagging on Docker Hub. This has been a known and recurring issue reported by multiple users across versions (1.6.2, 1.7.x, 2.0.1, etc.). [GitHub issue 70969; GitHub issue 61339] The knowledge sources do not contain the specific tag for

airbyte/async-profiler

that corresponds to Helm chart 2.1.1. I cannot tell you what tag to use without risking giving you incorrect information. Recommended approach: Run

abctl images manifest

against the 2.1.1 chart to get the exact tag. You can also check the Airbyte Helm chart values directly on GitHub for the 2.1.1 release tag to find the

asyncProfiler.image

value. Connector Builder Changes in 2.1.x There is a relevant change in Airbyte 2.1: the

connector-builder-server

component was removed from the Helm chart and replaced by a manifest server. [release notes] This means: • You no longer need to mirror

airbyte/connector-builder-server

for 2.1.x • A new manifest server image will be required instead • If you have

connectorBuilderServer.*

keys in your

values.yaml

, update them to

server.connectorBuilder.*

Tagging and Pushing Images Once you have the correct manifest, the general approach for your custom registry is: [custom registry docs]

abctl images manifest | xargs -L1 -I{} docker tag {} YOUR_REGISTRY/{} && docker push YOUR_REGISTRY/{}

And your

values.yaml

should reference your registry: [step 1 docs]

global:
  image:
    registry: YOUR_REGISTRY
  imagePullSecrets:
    - name: regcred

Bottom line: Use

abctl images manifest

or inspect the 2.1.1 Helm chart directly on GitHub to get the authoritative image list — the knowledge sources don't contain the specific tags for 2.1.1. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai abctl cannot be used

The knowledge sources do not contain enough information to give you the definitive image list (with tags) for Helm chart 2.1.1 without using

abctl

. However, here are some alternative approaches to find the correct images and tags: 1. Inspect the Helm chart directly — Pull the chart and look at the default `values.yaml`:helm pull airbyte-v2/airbyte --version 2.1.1 --untar cat airbyte/values.yamlThis will show you every image and tag the chart references, including

asyncProfiler.image

. 2. Check the Airbyte GitHub repository — The platform values file is publicly available. Look at the airbyte-platform repository at the tag corresponding to your release for the chart's

values.yaml

. Key things to note for 2.1.x specifically •

connector-builder-server

is removed — do not mirror it. It has been replaced by a manifest server image. [release notes] •

airbyte/async-profiler

— the knowledge sources do not confirm whether this image is still present in 2.1.1 or what tag it uses. Inspecting the Helm chart's

values.yaml

directly (as above) is the safest way to confirm this. • Helm chart V1 is no longer supported as of 2.1.0, so ensure you are using the V2 chart. [release notes] I'd strongly recommend the

helm pull

approach as the most reliable way to get the exact image list when

abctl

is not available. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.