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

Ability to provide the TLS secret name #119

Merged
merged 3 commits into from
Feb 12, 2024
Merged

Conversation

dzsak
Copy link
Contributor

@dzsak dzsak commented Feb 12, 2024

No description provided.

@dzsak dzsak linked an issue Feb 12, 2024 that may be closed by this pull request
Comment on lines 41 to 45
{{- if .ingress.secretName }}
secretName: {{ .ingress.secretName }}
{{ else }}
secretName: {{ printf "tls-%s" $resourceName }}
{{- end }}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might also work:

Suggested change
{{- if .ingress.secretName }}
secretName: {{ .ingress.secretName }}
{{ else }}
secretName: {{ printf "tls-%s" $resourceName }}
{{- end }}
secretName: {{ .ingress.secretName | default (printf "tls-%s" $resourceName) }}

@laszlocph laszlocph merged commit c56f637 into master Feb 12, 2024
2 of 6 checks passed
@laszlocph laszlocph deleted the provide-tls-secret-name branch February 12, 2024 15:30
@anbraten
Copy link

Thanks for the help ❤️

@laszlocph
Copy link
Contributor

Thanks for spotting this. I was really under the impression that we support this.

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.

Allow to set the ingress tls secretName
3 participants