[Feature request] Define admin username and passowrd using kubernetes secret, not directly in values #169

New Issue

2021-06-08T12:00:58Z

lord-kyron commented

2021-06-08 12:00:58 +00:00

(Migrated from gitea.com)

Hi all,
I think in cases (like mine) when using FluxCD with Helm Operator and my helm values files are sitting in git repo, having the admin username and pass configured there is really insecure. That is why I think that it will be best if you guys make support for admin username and password to come from existing secret in kubernetes.
That way we can use the sealed secrets extension to encode the username and password in the git repo and this chart to take it from the created kubernets secret directly instead of hardcoding them in plain text!

Thanks!

Hi all, I think in cases (like mine) when using FluxCD with Helm Operator and my helm values files are sitting in git repo, having the admin username and pass configured there is really insecure. That is why I think that it will be best if you guys make support for admin username and password to come from existing secret in kubernetes. That way we can use the sealed secrets extension to encode the username and password in the git repo and this chart to take it from the created kubernets secret directly instead of hardcoding them in plain text! Thanks!

luhahn commented

2021-06-08 14:08:37 +00:00

(Migrated from gitea.com)

True, there was some similiar request to this one. Haven't had time but I might have a nice idea in how to include it. Will try and prepare a PR for this :)

luhahn commented

2021-06-08 15:44:28 +00:00

(Migrated from gitea.com)

Done, feel free to test this :) #170