Skip to content
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

Helm-Chart: make the MySQL-Secret optional #5582

Closed
gtudan opened this issue May 13, 2024 · 1 comment
Closed

Helm-Chart: make the MySQL-Secret optional #5582

gtudan opened this issue May 13, 2024 · 1 comment

Comments

@gtudan
Copy link
Contributor

gtudan commented May 13, 2024

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.

@gtudan 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
@gtudan
Copy link
Contributor Author

gtudan commented 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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant