It is not possible to specify an existing ServiceAccount #280
Description
I use vault-secrets-a webhook that allows me to get secret data from HashiCorp Vault. This action requires the use of ServiceAccount with the name specified in the Vault. I usually create a ServiceAccount separately in a namespace or create it only in one place in the chart. In this case, I need this functionality for both the OpenWebUI chart and its Pipelines dependency, but ServiceAccount is always created there, which ruins the logic of work. I suggest introducing an additional parameter in values, which will determine whether it is necessary to create a ServiceAccount or whether an existing one can be used.
The change looks simple, so I'll study the guideline and try to prepare the Pull Request during today.