Took some liberties to give a user the ability to toggle over sharing permissions when it came to the helm chart functionality. (helm needs kubernetes secrets)
Restart cron manifests are to avoid OOMKill restarts since it looks like the memory just strictly grows over time.
I hoped to not make this too complicated even though I know it's fairly common to expose the knobs for things like readiness and liveness probes. I'll add any of those knobs if you deem it necessary
This simply takes what is in the config file and pushes them into a configmap. Which depending on the configuration can be complicated given the number of passwords in there. Supporting env vars for config could alleviate this, end users to this helm chart can kustomize patch their way to making it work. They could also use some init scripts / containers etc to get secrets in the right place. Or supporting multiple config files that get merged together, separate config files contain separate mounted secrets mounted from kube secrets.
arminc
commented
2 years ago
Closes #12
I hoped to not make this too complicated even though I know it's fairly common to expose the knobs for things like readiness and liveness probes. I'll add any of those knobs if you deem it necessary
This simply takes what is in the config file and pushes them into a configmap. Which depending on the configuration can be complicated given the number of passwords in there. Supporting env vars for config could alleviate this, end users to this helm chart can kustomize patch their way to making it work. They could also use some init scripts / containers etc to get secrets in the right place. Or supporting multiple config files that get merged together, separate config files contain separate mounted secrets mounted from kube secrets.