remove dependency on cert-manager, so trust-manager can be installed via vcluster clusters

[lknite]

vocabulary:

• host cluster: the cluster a vcluster is running in

vcluster:

• vcluster lets you spin up a k8s cluster, which is deployed using an existing cluster
• the vcluster uses the 'host cluster' worker nodes as if they are the vcluster's worker nodes
• an app running in vcluster only knows about vcluster, it doesn't realize its using resources on the host cluster

vcluster sync (between host and vcluster):

• vcluster offers some sync options such as to sync the storage classes of the host cluster with the vcluster, so they can be seen within the vcluster
• ingress, this allows an ingress to exist in the vcluster, but actually be implemented via controllers on the host cluster

I think trust-manager may just work if installed in a vcluster, if it doesn't have the cert-manager requirement. Because, the cert-manager is there in the host-cluster, and maybe whatever trust-manager needs is actually going to work with trust-manager.

Is someone involved with this project already using vcluster & have trust-manger working with it?

[erikgb]

We should probably support an installation not requiring cert-manager. There is a stale PR here: https://github.com/cert-manager/trust-manager/pull/157

This issue might be considered a possible duplicate of https://github.com/cert-manager/trust-manager/issues/132.

[SgtCoDFish]

Hey, thanks for raising this! Gonna close since I think #157 solves this. We might want future ways of doing this that don't rely on helm but the next release of trust-manager will contain this change 👍

[lknite]

I found a work-around here: https://github.com/loft-sh/vcluster/tree/main/generic-sync-examples/cert-manager

I think its fair to say this is a fix on the vcluster side and not specific to trust-manager