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
extraEnv in this chart is a list currently where its elements gets rendered under env without additional parsing. The downside of this is that declaring extraEnv from two config files leads to overriding the list instead of appending or replacing individual entries.
Current status
# current config syntaxextraEnv:
- <k8s native env element, not manipulated by the chart besides applying `tpl`>
- ...
It supports configuring extraEnv in several ways, which added notable complexity and made it hard to understand what it renders to and how to configure it without reading the configuration reference.
extraEnv
in this chart is a list currently where its elements gets rendered underenv
without additional parsing. The downside of this is that declaring extraEnv from two config files leads to overriding the list instead of appending or replacing individual entries.Current status
Current rendering logic:
binderhub-service/binderhub-service/templates/deployment.yaml
Lines 56 to 58 in 4f4cfec
jupyterhub chart current status
It supports configuring extraEnv in several ways, which added notable complexity and made it hard to understand what it renders to and how to configure it without reading the configuration reference.
See the Deployment template's env specification, and the referenced chart helper function.
Proposal
extraEnv
be an object instead of a list (breaking change)So in practice, this means to do it like z2jh, but with the differences of:
extraEnv
as a listhub.extraEnv
extraEnv
key's values usingtpl
The text was updated successfully, but these errors were encountered: