-
Notifications
You must be signed in to change notification settings - Fork 70
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
Why duplicate login credentials in values? #250
Comments
Because on of these values confiures the zammad chart and the other the postgres sub chart. In the end these are just the default values so that the zammad chart can be easily deployed. In production, where your config likely resides in a git repo, secrets should never be a part of it. |
yeah mine are also deployed via gitops, still it adds opportunity to screw up in the config - and I know many other charts where you only need to add the password once so there is apparently some way to access the values of the subchart |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
this should be a fairly quick fix but I don't have the proper experience here |
In the values.yaml you have
zammadConfig.postgresql.pass
andpostgresql.auth.password
, stating explicitly that they need to be the same - why not just default one to the other so filling in one is sufficient? Same for redis, but interestingly not for minio it seems.The text was updated successfully, but these errors were encountered: