It seems like the only way to create the secret is by providing the values directly in the helm values. In cases where infrastructure as code is used, this is very unsafe and instead the secret can be loaded from an external source, and provided to the deployment using a custom certificate.
This means that the values.yaml file should have a section to allow to provide your own custom secretRef, and then it be used for the deployment.yaml template.
It seems like the only way to create the secret is by providing the values directly in the helm values. In cases where infrastructure as code is used, this is very unsafe and instead the secret can be loaded from an external source, and provided to the deployment using a custom certificate.
This means that the values.yaml file should have a section to allow to provide your own custom secretRef, and then it be used for the deployment.yaml template.