Provide a way to securely store oauth

[Keramblock]

mb I miss something, but right now we forced to use configmap provided by helm chart itself to store data we need to work with oauth. MB better to at least allow to provide it from secret outside of helm chart or by file specified in container, so we could mount them there.

[kolesnikovae]

Thank you for reporting the issue @Keramblock! Indeed, we lack this option. What do you think about using env variables, instead of the ConfigMap, as per the suggestion - #41 (comment) (not implemented yet)?

MB better to at least allow to provide it from secret outside of helm chart or by file specified in container, so we could mount them there.

It definitely makes sense. We already have extraVolumeMounts but the container args are hardcoded - to be fixed as well.

[Keramblock]

env variables, instead of the ConfigMap,
Currently we using Hashicorp Vault to securely work with secrets in k8s, so we could create secret from it, or pass file to pod using annotations via injector. So env variables would be viable, if we could pass them from secret to pod, using something like .Values.additionalEnvs