You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
From v1.2, All the Argo CD workloads in the default Instance namespace are deployed with resource requests/limits by default. The current resource requests and limits set on the repo server is:
However, many users have reported OOM issues on the repo-server. Looking at the issues I think we would need to upgrade the memory from 512Mi to 1024Mi
To Reproduce
Steps to reproduce the behavior:
run the operator from the console or from the CLI using operator-sdk run local
Move to Workloads -> Deployment -> openshift-gitops-repo-server and look at the memory limit that is set.
Expected behavior
OOM crash should be avoided.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
From v1.2, All the Argo CD workloads in the default Instance namespace are deployed with resource requests/limits by default. The current resource requests and limits set on the repo server is:
However, many users have reported OOM issues on the repo-server. Looking at the issues I think we would need to upgrade the memory from
512Mi
to1024Mi
To Reproduce
Steps to reproduce the behavior:
operator-sdk run local
openshift-gitops-repo-server
and look at the memory limit that is set.Expected behavior
OOM crash should be avoided.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: