Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4602

HA config option for larger repos in OpenShift GitOps

XMLWordPrintable

    • 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/

      [2] https://argocd-operator.readthedocs.io/en/latest/reference/api.html/#argoproj.io/v1alpha1.ArgoCDRepoSpec

       

              jgwest Jonathan West
              rhn-support-dtambat Darshan Tambat
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: