Application controller OOMKilled - proposed fix to increase memory limit

[ctari1]

Hi team,

I’ve opened a pull request to increase the memory limit for the Argo CD application controller deployed by the operator. In our environment, the controller frequently crashes due to being OOMKilled, and raising the memory limit resolves the issue.

    lastState:
      terminated:
        containerID: cri-o://c3473a1a31435a92ad33650e9adc53da66f02c8d2bb5d15e2fb0d051d74634b2
        exitCode: 137
        finishedAt: "2025-10-16T12:42:57Z"
        reason: OOMKilled
        startedAt: "2025-10-16T12:42:45Z"

Current resource usage:

NAME                                                          CPU(cores)   MEMORY(bytes)
cluster-5dfc445794-gm8zp                                      1m           44Mi
gitops-plugin-647d6b4fd5-544mr                                1m           43Mi
openshift-gitops-application-controller-0                     1892m        4703Mi
openshift-gitops-applicationset-controller-7c85765dc4-vgtvn   1m           44Mi
openshift-gitops-dex-server-9f77fbf9-bbchw                    1m           184Mi
openshift-gitops-redis-757977b54c-dgl7k                       3m           16Mi
openshift-gitops-repo-server-5c958cd885-jxw79                 18m          68Mi
openshift-gitops-server-56f745455f-m9cr2                      1m           93Mi

#445

Please review the PR when you have a chance.

[darkdoc]

Hey!
Reasonable change! Merged that PR, and added a quick fix to the unit tests
#447
We can do a new version of the operator sometimes around next week.

[ctari1]

Thanks, we'll keep the operator scaled down 0 in the meantime.
Sorry about the failing unit tests.

/Krisztian