-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.11.1
-
False
-
None
-
False
-
-
Description of problem:
Ability for OpenShift Gitops to handle larger gitops repos
Prerequisites (if any, like setup, operators/versions):
GitOps 1.11.1
Actual results:
Fails due to out of disk space
Expected results:
Deploys helm charts successfully
Additional info (Such as Logs, Screenshots, etc):
The ArgoCD HA guidelines [1] says:
> argocd-repo-server clones the repository into /tmp (or the path specified in the TMPDIR env variable). The Pod might run out of disk space if it has too many repositories or if the repositories have a lot of files. To avoid this problem mount a persistent volume.
However the Gitops/ArgoCD operator doesn't support setting this [2]. This means we're unable to use large git repos with OpenShift Gitops currently.
[1] https://argo-cd.readthedocs.io/en/stable/operator-manual/high_availability/
- depends on
-
GITOPS-2107 openshift-gitops-application-controller-0 is using /dev/shm as temporary directory which can eventually be used up as it's limited to 64M
- In Progress