You can create your own Helm chart with the ClusterIssuer and configure it to *depend* on the published cert-manager chart.
The trouble is that Helm might try installing the ClusterIssuer before the cert-manager webhook TLS is configured:
I have not tried it myself, but perhaps you could use a Helm pre-install hook in *your* chart which blocks until the cert-manager API is usable, by performing `kubectl apply -f test-resources.yaml --dry-run` in a loop until it succeeds:
If you succeed in getting this working, please consider documenting it for the benefit of other cert-manager users:
We've been discussing this problem in Slack today, in case you'd like to weigh in:
Thanks and good luck