[Feature request] Define admin username and passowrd using kubernetes secret, not directly in values #169
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#169
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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!
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 :)
Done, feel free to test this :) #170
Seems working fine! Thank you for the quick reaction!
When can we expect this to be merged to master branch?
@lord-kyron just released 3.1.4 containing the update