You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working on Litmus Chaos custom installation for a while and noticed that currently there's no way to set your own custom environment variables for any Litmus pods. At least that I'm aware of.
It can be useful for users to configure their own env vars for different purposes. As a good example, setting HTTP_PROXY can be one of those.
They support extraEnvVars parameter defined in Helm chart as well as extraEnvVarsCM that come from configmaps and also extraEnvVarsSecret that come from secrets.
Please consider implementation of some kinda functionality that mocks extraEnvVars, so that the users can set their own things. Especially when it comes to HTTP_PROXY it can be crucial for the tool functionality.
The text was updated successfully, but these errors were encountered:
Greetings,
I've been working on Litmus Chaos custom installation for a while and noticed that currently there's no way to set your own custom environment variables for any Litmus pods. At least that I'm aware of.
It can be useful for users to configure their own env vars for different purposes. As a good example, setting HTTP_PROXY can be one of those.
Bitnami MongoDB Helm chart used in litmus-helm as a subchart implements it this way:
They support extraEnvVars parameter defined in Helm chart as well as extraEnvVarsCM that come from configmaps and also extraEnvVarsSecret that come from secrets.
Please consider implementation of some kinda functionality that mocks extraEnvVars, so that the users can set their own things. Especially when it comes to HTTP_PROXY it can be crucial for the tool functionality.
The text was updated successfully, but these errors were encountered: