You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by "jwitko (via GitHub)" <gi...@apache.org> on 2023/02/14 20:18:13 UTC

[GitHub] [druid] jwitko commented on pull request #13796: helm: Add customizable global and per-container env vars to helm chart

jwitko commented on PR #13796:
URL: https://github.com/apache/druid/pull/13796#issuecomment-1430322198

   > to understand, this allow for more than just name, value envVars, so you can do ValueFrom and grab things from secrets, or other places?
   Yes correct.  It also allows you to direct the key/values inside configmaps/secrets to be populated into an envVar of your choice.  In my example in this PR I'm taking the dynamically generated postgresDB secret which is created by a postgresDB operator and pushing it into the Druid accepted envVar for DB passwords.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org