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

Missing STRICT_COMPARISON_NORMALIZATION_WORKSPACES and STRICT_COMPARISON_NORMALIZATION_TAG from configmap helm chart #22687

Closed
Utwo opened this issue Feb 9, 2023 · 2 comments · Fixed by airbytehq/airbyte-platform#52
Labels
area/platform issues related to the platform area/worker Related to worker community helm team/compose type/bug Something isn't working

Comments

@Utwo
Copy link
Contributor

Utwo commented Feb 9, 2023

Environment

  • Airbyte version: helm-chart-0.43.33
  • OS Version / Instance: GCP
  • Deployment: Kubernetes

Current Behavior

When I'm trying to install airbyte using the Helm Chart I get an error that STRICT_COMPARISON_NORMALIZATION_TAG and STRICT_COMPARISON_NORMALIZATION_WORKSPACES are missing from configmap airbyte/airbyte-airbyte-env but required by airbyte-worker.

Expected Behavior

Helm chart should be installed successfully.

Steps to Reproduce

Install the helm chart 0.43.33 with the default values.
Check the worker deployment.

$ kubectl describe deployment airbyte-worker

You should see an error similar to:

couldn't find key STRICT_COMPARISON_NORMALIZATION_TAG in ConfigMap airbyte/airbyte-airbyte-env

Are you willing to submit a PR?

Of course

@Utwo Utwo added needs-triage type/bug Something isn't working labels Feb 9, 2023
@yuriolive
Copy link

Having the same issue here.

@yuriolive
Copy link

Temporary solution is to use Helm chart version 0.43.29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/platform issues related to the platform area/worker Related to worker community helm team/compose type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants