You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The seaweedfs helm chart uses a secret to deploy the filer database credentials for MySQL. We don't Redis in our setup, so we don't really need those credentials. We would prefer not to have them, as the defaults are hardcoded. Making them optional would allow us to remove them, without breaking the deployment.
System Setup
Seaweedfs deployed via Helm
Helm 3 on Kubernetes 1.27
Helm chart 3.67
Redis as filer persistence (or any non-mysql datastore)
Expected behavior
It is possible to remove the database secert without breaking the deployment.
The text was updated successfully, but these errors were encountered:
gtudan
changed the title
Allow using an existing secret for the database in the helm chart
Helm-Chart: make the MySQL-Secret optional
May 13, 2024
I didn't want to put this into the description in order not to sidetrack the ticket - but is there a specific reason to include the MySQL-Config in the chart, although it is not enabled? It would still be possible to configure MySQL through the extraEnvironmentVars / secretExtraEnvironmentVars (like all other persistence options).
Describe the bug
The seaweedfs helm chart uses a secret to deploy the filer database credentials for MySQL. We don't Redis in our setup, so we don't really need those credentials. We would prefer not to have them, as the defaults are hardcoded. Making them optional would allow us to remove them, without breaking the deployment.
System Setup
Expected behavior
It is possible to remove the database secert without breaking the deployment.
The text was updated successfully, but these errors were encountered: