-
Bug
-
Resolution: Done
-
Major
-
1.11.1
-
13
-
False
-
None
-
False
-
-
-
GitOps Scarlet - Sprint 3259, GitOps Scarlet - Sprint 3260
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/
- is related to
-
GITOPS-4646 Provide option to use persistent volumes for Repo server Storage
- Closed
- links to
-
RHEA-2024:137049 Errata Advisory for OpenShift GitOps v1.14.0