Provide possibility to set additional environment variables

[sebastiangaiser]

Is your feature request related to a problem? Please describe. I tried to find a problem during setting up Waypoint on Kubernetes. For this I tried to change the default log level of waypoint. I didn't found a possibility to change the log level in the Helm chart

Describe the solution you'd like Please provide a general possibility to set additional environment variables by Helm (not only limited to the log level).

Describe alternatives you've considered Editing the StatefulSet manually is not so nice...

...
env: 
 - name: HOME 
   value: /home/waypoint 
 - name: WAYPOINT_LOG_LEVEL 
   value: TRACE
...

Another possibility would be to create a configmap for the server and couple the ConfigMap and the StatefulSet by a hash.

[izaaklauer]

Hi @sebastiangaiser ,

You can increase the log level of the waypoint server to trace by giving -vvv as a server runArg: https://github.com/hashicorp/waypoint-helm/blob/7ce6f6354b51750789f4199e129bfd4f41b22bec/values.yaml#L19-L20

You can also change the log level of the waypoint on-demand runners by running waypoint config set -runner WAYPOINT_LOG_LEVEL=debug.

That said, there isn't a great way to set the server log level below info, or to change the static runner's log level. PR to address that here: https://github.com/hashicorp/waypoint-helm/pull/17

[sebastiangaiser]

@izaaklauer exactly, there is a workaround but that's not a nice way todo it.

[izaaklauer]

Would you want a more accessible flag that would change the log level of all the waypoint systems (server, runner, remote runners) across the board, or were you just aiming for the server?

[k21205]

I am running the cluster behind a Proxy, so I need to be able to manipulate environment variables to give access to the VCS