Deployment of new operators and CustomResources via ArgoCD failed with CR not found

Solution Verified - Updated -

Issue

  • Installing the OpenShift Operator and its specific CustomResources(CRs) through ArgoCD failed with the error even after using sync-wave:

    <CR>.operator.openshift.io "" not found
For Example:
CertManager.operator.openshift.io "" not found

Environment

  • Red Hat OpenShift Container Platform(RHOCP)
    • 4.x
  • Red Hat OpenShift GitOps
    • 1.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content