How to modify environment variables for Kubernetes job after switching from PostgreSQL to MySQL in Dagster

[Shahrullo]

What's the issue or suggestion?

Hello, I have a question about modifying environment variables for a Kubernetes job. I have modified the Dagster Helm chart to switch the storage backend from PostgreSQL to MySQL instead. The webserver and daemon components are working fine with the new MySQL configuration, but the code-user deployment is still expecting the PostgreSQL password environment variable.

When I look at the job logs for the code-user deployment, I see the following:
DAGSTER_PG_PASSWORD: .

In the current Helm chart configuration, there are no variables related to PostgreSQL. I believe the issue might be within the code-user Docker image itself, where the PostgreSQL environment variable is still being expected.

How can I modify the environment variables for this Kubernetes job (specifically the code-user deployment) to use the MySQL password instead of the PostgreSQL password?

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[Shahrullo]

I have found a solution to the issue. The Kubernetes Dagster cluster is now using MySQL instead of PostgreSQL. However, this is not an optimal solution as the PostgreSQL environment variables are hard-coded within the Python packages. In the future, I plan to modify the packages and submit a pull request to address this issue more comprehensively.