-
Notifications
You must be signed in to change notification settings - Fork 161
Allow setting existing secret name for TLS certs #233
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: master
Are you sure you want to change the base?
Conversation
@bokysan Is there any chance to have this added or something that would allow the controlling of the secret name |
Hey @mrskul, thank you for the commit. Seems almost OK, I've left a comment. If you can fix this, we can merge it. |
@bokysan Happy to fix this but i don't see the comment. |
helm/mail/templates/_helpers.tpl
Outdated
{{- if $secretName -}} | ||
{{- printf "%s" (tpl $secretName .) -}} | ||
{{- else -}} | ||
{{- printf "smtp-relay-mail-certs" -}} | 8000
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.
You have hardcoded a name here. Previously this was {{ $fullName }}-certs
, but is now hardcoded. Please fix this.
@@ -129,6 +129,8 @@ certs: | |||
create: false | |||
# Provide existing cert | |||
existing: false | |||
# Provide existing secret name | |||
existingSecret: "" |
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 am missing:
- documentation (we should say something in
README.md
) - tests (see https://github.com/bokysan/docker-postfix/tree/9fcd02f67ca753cb4c2fa06c44104b6d8a24c485/helm) -- tests are necessary to ensure that helm always generates proper YAML.
I'm sorry. My mistake - didn't click 'Finish review'. Should be visible now. |
It would be helpful to have a method for controlling the TLS secret name, as this would allow users to reference an existing secret and manage the name themselves. This is particularly useful when reflecting secrets from other namespaces, where renaming the secret may not be possible.