-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make persistent secret generation for adminSecret
#74
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
This is related to #7 , although that issue seems a bit dated. Basically, when
createAdminSecret
is used (by default), a new secret seems that it will be generated on each release (I have yet to verify myself).Describe the solution you'd like
In line with #73 , it is possible to generate values in such a way that they can be used consistently and preserved within Kubernetes (along with an optional user notification).
Describe alternatives you've considered
Putting the work onto the user to maintain / change these values (as is currently done)
Additional context
Depending on the outcome of #73, this would be fairly straightforward to implement within the helm chart. Wording and whether/how to notify in
NOTES.txt
(i.e. once for each value? Something less verbose?) will be important to consider.The text was updated successfully, but these errors were encountered: