-
Couldn't load subscription status.
- Fork 110
Add additional configuration for redis secrets #201
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
base: main
Are you sure you want to change the base?
Conversation
| name: {{ template "mastodon.redis.secretName" . }} | ||
| {{- end }} | ||
| key: redis-password | ||
| key: {{ .Values.redis.auth.existingSecretKey }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better to have both name and key (the whole secretKeyRef be from a template, rather than repeating this everywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's honestly not a bad idea. I'll make that change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Except I can see one issue with this.
The current solution allows it to be backwards compatible with the way it's already done. This new solution would basically mean either replacing existingSecret with that new format, which would break existing setups, or creating a new field like existingSecretRef, which wouldn't break anything, but would be somewhat redundant.
Allows users to set the existing secret key for redis instances. Default values are still set in such a way that the chart will behave the same as before by default.
This change makes it easier for me personally to set up some new infrastructure in a way that's better conforms to standards.