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

[ISSUE] add optimize env vars to migration init container #2709

Open
drodriguez-305 opened this issue Dec 19, 2024 · 0 comments · May be fixed by #2710
Open

[ISSUE] add optimize env vars to migration init container #2709

drodriguez-305 opened this issue Dec 19, 2024 · 0 comments · May be fixed by #2710
Assignees
Labels
kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between kind/medic Tasks for the medic platform/aws Issues related to AWS platform/gcp Issues related to GCP support Marks an issue as related to a customer support request (don't edit the lable)

Comments

@drodriguez-305
Copy link
Contributor

Describe the issue:
related to: https://jira.camunda.com/browse/SUPPORT-25039

The optimize.env values are not included in the migration init container's env section, resulting in missing environment variable configurations for Optimize during migrations.

Actual behavior:
Since some of the envars from optimize are not being passed it can cause issues with upgrading. In this instance the prefix was not being passed and caused issues. This fix should cover those scenarios.

Expected behavior:
The migration init container should include both:

{{- with .Values.optimize.migration.env }}
{{- with .Values.optimize.env }}

This ensures all necessary environment variables are properly applied for migrations and runtime configurations.

How to reproduce:

Logs:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

  • Platform:
  • Helm CLI version:
  • Chart version:
  • Values file:
@drodriguez-305 drodriguez-305 added kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between support Marks an issue as related to a customer support request (don't edit the lable) kind/medic Tasks for the medic labels Dec 19, 2024
@drodriguez-305 drodriguez-305 added this to the 8.7 Release Cycle milestone Dec 19, 2024
@github-actions github-actions bot added platform/aws Issues related to AWS platform/gcp Issues related to GCP labels Dec 19, 2024
@drodriguez-305 drodriguez-305 self-assigned this Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/issue Unidentified issue, it could be a bug, misconfig, or anything in between kind/medic Tasks for the medic platform/aws Issues related to AWS platform/gcp Issues related to GCP support Marks an issue as related to a customer support request (don't edit the lable)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant