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

Allow user to customize all tenant environment variables #1137

Merged
merged 1 commit into from
May 21, 2022

Conversation

Alevsk
Copy link
Contributor

@Alevsk Alevsk commented May 20, 2022

  • variables defined in tenant.spec.env will take precedence over
    default/hardcoded values
  • if a variable exists on the config.env configuration file operator
    will not pass it to the pods via container.spec.env

Signed-off-by: Lenin Alevski alevsk.8772@gmail.com

@Alevsk Alevsk self-assigned this May 20, 2022
dvaldivia
dvaldivia previously approved these changes May 20, 2022
@Alevsk Alevsk force-pushed the custom-env-vars branch from 037cb62 to 986faf1 Compare May 20, 2022 23:24
@Alevsk Alevsk requested a review from dvaldivia May 20, 2022 23:25
@Alevsk Alevsk force-pushed the custom-env-vars branch 2 times, most recently from 08c847a to 2e2d931 Compare May 20, 2022 23:35
@Alevsk Alevsk requested review from cniackz, kanagarajkm and krisis May 21, 2022 00:36
- variables defined in `tenant.spec.env` will take precedence over
  default/hardcoded values
- if a variable exists on the config.env configuration file operator
  will not pass it to the pods via container.spec.env

Signed-off-by: Lenin Alevski <alevsk.8772@gmail.com>
@Alevsk Alevsk merged commit 854e1dd into minio:master May 21, 2022
@Alevsk Alevsk deleted the custom-env-vars branch May 21, 2022 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants