[ISSUE] add optimize env vars to migration init container #2709
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)
Milestone
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:
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.
The text was updated successfully, but these errors were encountered: