Why Deployment resources section remains OutOfSync in Openshift Gitops ?

Solution Verified - Updated -

Issue

  • ArgoCD application remains in OutOfSync status even though the cpu, memory is same in live and desired manifest. Only difference is that the unit of the resource values are converted.
  • cpu, memory resource value remains in OutOfSync status even though the values are same between live and desired manifest.
    resource in OutOfSync status
    resource in OutOfSync status

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift GitOps

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