Sensitive Mailer config settings via Kubernetes secrets #174
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: lunny/helm-chart#174
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 again,
for the same security purposes I requested the admin username and password to be able to put in k8s secrets, now I remembered, that the SMTP (Mailer) username and password are also sensitive info and can also be put under k8s secrets.
Can you again,please, implement this change if possible?
Thank you!
Not only the username and password of the mailer should be protected by a secret, the database credentials should also be secured by a secret!
Same for oauth. ?
EDIT: https://gitea.com/gitea/helm-chart/issues/242
@luhahn @lunny can youguys check this one,please ?
I will try to implement this next week. It will be a bigger change because we will need to add env var parsing to the init container and infuse it into the app.ini
Sorry to bother you guys (you're doing a fantastic job!!), but are there any news on this issue?
Yes guys, I am still waiting for this feature to be available.
@lord-kyron
Afaik there is no progress on this issue.
We all do this in our spare time and it seems that there is not much of it in the past months. Any help (whether ideas on how to implement things or even providing PRs) is highly appreciated.
? Gitea is smarter than me with referencing issues.
? Don't know what I got wrong last time. Mailer config is inside
app.ini. #240 will actually resolve this and even allow for more flexibility so that database credentials can be provided in a secure manner.