[Request] Add ability to add additional env variables

[grzesuav]

Describe the feature

I would like to switch logging to JSON - https://quarkus.io/guides/logging#configuration so setting the env var - apparently is shoudl be done by QUARKUS_LOG_CONSOLE_JSON. It is not possible to add any right now

Anything other information?

No response

[andrewazores]

You can install using the Helm chart and then manually edit the Deployment that it creates afterward. But I agree, it would be nice to be able to specify these things at installation time.

[andrewazores]

I'm thinking of maybe adding something like this:

core:
  config:
    extra:
      configMapName: ""

If the user creates a ConfigMap and installs with --set core.config.extra.configMapName=my-cm, then the cryostat-deployment.yaml template could check whether a ConfigMap name was provided and if it was, mount that to the Cryostat container environment variables. It'll be up to the user to make sure they aren't causing conflicts with other environment variables set by other top-level configuration options.

https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables

[andrewazores]

^ we could do the same for the other deployments too quite easily, ex.

reports:
  config:
    extra:
      configMapName: ""

Maybe we also need a way to specify per-container ConfigMaps, since at least the main Deployment actually contains Cryostat, jfr-datasource, Grafana dashboard, and an optional auth proxy. So far this plan would only allow for setting additional environment variables on the Cryostat container, or else setting environment variables that would be applied to every container in the Pod.

[andrewazores]

@tthvo has the best proposal here, significantly expanding on what I had above:

#247 (comment)

[grzesuav]

sounds great !