Trouble changing Airbyte container image in Kubernetes deployment

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

When changing the orchestrator container image in the Kubernetes YAML file for Airbyte, the new image is not applied to the jobs, and Airbyte’s default image is still used. The user also needs to change the image for the Socat and connector sidecar.


Question

I’m deploying Airbyte on Kubernetes, version 0.64.1, and we’ve been facing issues with Docker Hub image pull limits. As a workaround, we started duplicating the images to a private repository. However, when I change the orchestrator container image in the YAML file, the change is not applied to the jobs, and Airbyte’s default image is still used. Below is the section where I defined the image (I’ve placed it in two spots based on the YAML examples I found):

   containerOrchestrator:
   # -- Orchestrator image
   image: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
   tag: 0.64.1

workload-launcher:
   containerOrchestrator:
   # -- Orchestrator image
   image: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
   tag: 0.64.1```
I also need to change the image for the Socat and connector sidecar. Can anyone help me with this?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1728991895593059) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte", "kubernetes", "docker-hub", "image-pull-limits", "private-repository", "yaml", "container-image", "sidecar"]
</sub>
2

Have you read my message in different thread?
https://airbytehq.slack.com/archives/C021JANJ6TY/p1728761440207539?thread_ts=1728759955.985099&amp;cid=C021JANJ6TY

3

yes, but as you can see, i’ve setted the worker container orchestrator image and for workload-launcher, but it doesnt worked… (containerOrchestrator in workload-launcher is setted to enabled)

4

no, there is no enabled: true in your example and image should be indented 2 spaces more, under containerOrchestrator
which helm chart version do you use?

5

my copy and paste didn’t respect the idention:

6

and which helm chart version do you use?

7

apiVersion: v2
appVersion: 0.64.1
dependencies:

8

ok, so 0.524.0 is your version

9

it looks like you need to add the same environment variables from extraEnv under worker to extraEnv under workload-launcher

10

i didn’t set the workload-launcher extraEnv

11

yeah, and you need add those environment variables

12

in newer helm chart versions this is a bit improved

13

as I mentioned in different thread, you need to check specific helm chart and read the code
https://github.com/airbytehq/helm-charts
tar xzf airbyte-0.524.0.tgz

14

it worked! very thanks!

15

sorry if i missundertood before…