High memory utilization of `openshift-gitops-operator-controller-manager` pod Post upgrade to Gitops operator v1.14.0

Solution Verified - Updated -

Issue

  • There has been high memory utilization of openshift-gitops-operator-controller-manager pod post upgrade to Gitops operator v1.14.0.
  • The POD openshift-gitops-operator-controller-manager in openshift-operators continue to CrashLoopBackOff due to OOMKilled.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • OpenShift GitOps
  • 1.14 and later

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