-
Notifications
You must be signed in to change notification settings - Fork 344
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
Being able to set environment variables using 'envFrom' #397
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What about this PR? Do you need anything else? |
+1 to that. |
@sgrzemski sorry, I'm confused but what should I do for that check? This is not obvious to me :/ |
@SmaineTF1 : |
Should I do something anyway @sgrzemski please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the submission, happy to work with you on getting this merged. Please can you rebase this against master.
@@ -84,6 +84,8 @@ server: | |||
additionalVolumes: [] | |||
additionalVolumeMounts: [] | |||
additionalEnv: [] | |||
additionalEnvCM: [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use additionalEnvConfigMap
rather than using a contraction.
What was changed
Add the ability to define environment variables that come from configmaps or secrets
Why?
Make use of envFrom is pretty handy when, for instance you have all the environment variables defined in Secrets or Configmaps.
That way we only need to have this bit of code if we have all the config env vars in a secret