Why is an existing ArgoCD instance not updated after GitOps Operator update?

Solution Verified - Updated -

Issue

  • After updating GitOps Operator to version 1.3.2, the existing ArgoCD instances are not upgraded to 2.1.8, but stuck on the previous version 2.0.5
  • Any new ArgoCD instance created after the operator update has the correct version - 2.1.8

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.8.24
  • OpenShift GitOps Operator 1.3.2

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