Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[helm] couldn't find key JOB_KUBE_CONNECTOR_IMAGE_REGISTRY in ConfigMap airbyte/airbyte-airbyte-env #53215

Open
ilyaberd opened this issue Feb 7, 2025 · 2 comments

Comments

@ilyaberd
Copy link

ilyaberd commented Feb 7, 2025

Helm Chart Version

1.4.1

What step the error happened?

During the Sync

Relevant information

Upgrading Airbyte 1.1.0 to 1.4.0, using helm chart version 1.4.1.

Getting CreateContainerConfigError for airbyte-workload-launcher: couldn't find key JOB_KUBE_CONNECTOR_IMAGE_REGISTRY in ConfigMap airbyte/airbyte-airbyte-env

We would like to use the default public registry as in version 1.1.0.

Relevant log output

container "airbyte-workload-launcher-container" in pod "airbyte-workload-launcher-" is waiting to start: CreateContainerConfigError
@marcosmarxm
Copy link
Member

Are you using the global.jobs.kube.main_container_image_pull_secret variable or how are you defining this variable?

@ilyaberd
Copy link
Author

ilyaberd commented Feb 7, 2025

No, I don't use any custom kube image variables and JOB_KUBE_CONNECTOR_IMAGE_REGISTRY is not defined. I expect helm to use public Airbyte registry as in version 1.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants