Evaluates the ingress TLS secret name as a template before deciding whether to include or or omit the secretName field.
Fixed
Using an ingress TLS secret name template evaluating to an empty string resulted in the secretName field still being added to the ingress TLS config with an empty string value.
Benefits
Allows using a template that may or may not cause the secretName field to be present in the Ingress TLS config.
Possible drawbacks
I guess this takes away the ability to ever add the ingress TLS secret name as an empty string. But I'm not sure ever having that as empty string is a valid use case.
Description of the change
Evaluates the ingress TLS secret name as a template before deciding whether to include or or omit the
secretNamefield.Fixed
Using an ingress TLS secret name template evaluating to an empty string resulted in the
secretNamefield still being added to the ingress TLS config with an empty string value.Benefits
Allows using a template that may or may not cause the
secretNamefield to be present in the Ingress TLS config.Possible drawbacks
I guess this takes away the ability to ever add the ingress TLS secret name as an empty string. But I'm not sure ever having that as empty string is a valid use case.
Applicable issues
None
Additional information
Checklist
Chart.yamlhas been bumped according to Semantic Versioning.artifacthub.io/changeschangelog annotation has been updated inChart.yaml. See Artifact Hub documentation for more info.values.yamlfile.~