Helm Parameter tls.secretName is not templated

[ds-mwesener]

Current Behavior

Currently the secretName will be static set to:

Expected Behavior

Since we have two instances of the registry within one namespace.
We need to be able to set the secretName via the values.yaml because it is required within the association environment to have unique secretnames. Otherwise we get certificate issues when trying to call the ingress.

Steps To Reproduce

Deploy two instances of registry within one cluster with one certificate manager.

[marctuerke]

I'm having the same issue, since I want to use existing certificates from my cluster.