Cert Manager Handling

[Mtze]

Hi everyone,

I'm currently playing with your Helm charts and i think the current handling of certificates in the base chart is suboptimal.

The base chart always installs a production ClusterIssuer (even if there might already be one that should be used for theia) and assumes that a second, self-signed Issuer has to be installed as well. I guess this was implemented that way to simplify the dev setup, but for production use cases I think the certificate handling should be handled separately, of at least be configurable.

If you agree with my suggestion, I'd start implementing that and open an PR.

[jfaltermeier]

Hi, I agree that we should not force install the issuers, especially since we already allow using different issuers via the helm values.
So maybe having two additional values with which we can skip each of them would be great.
I would still like to have the option to install both issuers or either of them using our charts.

Please note that the self-signed issuer may be used for the cluster-internal custom-resource-conversion-service as well (https://github.com/eclipsesource/theia-cloud-helm/blob/main/charts/theia-cloud-crds/templates/conversion-webhook-certificate.yaml), so this one is not just for testing locally.