Skip to content

Conversation

@timetinytim
Copy link
Contributor

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.

@timetinytim timetinytim requested a review from renchap August 4, 2025 12:47
@timetinytim timetinytim self-assigned this Aug 4, 2025
name: {{ template "mastodon.redis.secretName" . }}
{{- end }}
key: redis-password
key: {{ .Values.redis.auth.existingSecretKey }}
Copy link
Member

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?

Copy link
Contributor Author

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.

Copy link
Contributor Author

@timetinytim timetinytim Aug 12, 2025

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.

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

Successfully merging this pull request may close these issues.

2 participants