When the cert-manager Operator is installed, a CertManager Custom Resource is automatically created. Similar to other Custom Resources, the configuration of these assets can be managed declaratively using OpenShift GitOps.

However, issues can arise when the CertManager resource is managed by OpenShift GitOps as the Custom Resource may be created before the asset that is managed by the cert-manager Operator and leads to a series of unexpected and/or undesirable results.

This type of situation can be mitigated by providing an option to allow another entity to manage the creation and lifecycle of the CertManager custom resource and let the cert-manager Operator take action based on the defined definition. 

This type of solution could be implemented by providing tunable options within the cert-manager Operator (such as an environment variable) that could be defined within the Subscription resource.

Always    

    1. Install the cert-manager Operator from OperatorHub
  
    

CertManager Custom Resource automatically created.