Allow setting specific certificate (like the existing wildcard cert) when a domain is reserved

[justngrok]

Description

When creating or setting a host on the ingress controller -- have the ability to assign a certificate to the new domain, instead of going out to Let's Encrypt to get certs.

Example:
If have the wildcard domain, which already has a wildcard certificate:
*.mydomain.com

And I create a new ingress controller with the host.

abc-123-def-456.mydomain.com

I don't want to wait for ngrok to go out to Let's encrypt to get certs, and would like the ability to just apply the wildcard cert that I already have, that matches the new host.

This could be done via the domain CRD? or with an option in the Ingress Controller deployment?

Alternative (may not be ingress-controller-related):
Make it optional to use an existing matching wildcard cert instead of getting a new cert when a new subdomain is reserved.

Use Case

Cromulence spins up/down environments quickly, delay in waiting for certificate that isn't necessary is causing delays in being able to use the environment.

Related issues

No response