Ability to template the secret output

[ryanfaircloth]

The standardized secret is great for applications where I can adopt the format. I can't do that with all legacy apps. Could we provide a template for the secret so for example an application that will only accept the kafka settings as specific env vars I could template the right key/values to simply replace an existing secret and use the new secret as envfrom:

[scholzj]

When you map Secret to Environment variables, you do not really care about the Secret structure. so I do not think I follow the request.

[ryanfaircloth]

Sometimes its a matter where for example for reasons of choices someone else made an existing applications cr asks for a secret with the env variables already properly named in the form of envFrom which doesn't let you map the secrets yourself they have to be pre-mapped. Having the ability to customize the secret as a template provides flexibility to work with existing choices where revisting those choices is for what ever reason off the table

[scholzj]

Honestly, it took us 2 and half years to get out the first release and several months to fix and finish the Helm Chart release. And it still does not fulfill the main goal which is the cross-cluster access. So I'm not sure we have the space to onboard issues like this.

[ryanfaircloth]

Fair, I suggest putting it in the backlog then. others will ask when it makes sense do it but not before

[katheris]

Triaged on 20.2.2025: The Secret is created with entries that match some popular libraries. We don't intend to add more flexibility unless we get more users requesting this, so closing this issue.